I've been glad to be able to provide support for you. I'm really looking forward to what you produce. I'm just starting to learn AmigaOS4 programming myself, so the more tools the better!

OK done - funded by the recent sale of my A1200 bits...

Next steps... get OS4.0 and some hardware that runs it... learn to code... profit?

_________________

Thanks Jamie
1st class customer service!

_________________
A1200T 603e 330Mhz - Mediator TX OS4.1 F.E.
CDTV 8MB Fast, OS3.1, SCSI, MicroSD SCSI & CD32 FMV
X5000, X1000, A1XE with OS4.1F.E.

Already a member but just wanted to stop in and say
thanks for all the great work.

_________________
Kevin - X1000 First Contact / A1222+

Just wondering if there's a status update you might want to mention? As in GuiBuilder ETA for final, and the next bit to be started?

_________________
Are we not done with the same silly arguments and flames yet??!

Great work, Jamie.
I am pleased to be supporting your efforts.

_________________
Moxee
AmigaOne X1000
AmigaOne XE G4
I'd agree with you, but then we'd both be wrong.

@wegster

Duh! I thought that you'd been active around here for long enough to know that you should *never* ask for an ETA of when something will be completed

_________________

Quote:

Just wondering if there's a status update you might want to mention? As in GuiBuilder ETA for final, and the next bit to be started?

Sure thing, I was just about to do one for the FDSP members but
I can do a small update report here:

OK, first of all the current development efforts are going mainly
into completing the GUI Builder component for public release.
A new update to which should release to FDSP members within
the next day or two and will include several bug fixes and some
newly added confirmation requesters, making it more friendly
to use by helping protect load/import/save and code generation
actions.

More features were planned for this release but with the
extensive number of changes between Update 3 and Beta OS4
I had to spend most of the time updating and testing the code
on my second A1 machine, which is running the latest Beta OS.
As a result the entire code base is now building using the latest
GCC 4.0.2, and things like "true" mouse-wheel support has been
added to both the SDK Browser and GUI Builder, making them
ready for Update 4.

I have one test machine here which is setup to run and build using
the latest public release (currently Update 3), and one which is kept
up-to-date with the latest is Beta releases from the OS4 development
team.

The GUI Builder component is very central to AVD as a whole and
as such will support several code building and runtime options for
it's output. Here is what is currently being implemented:

1.) C source output for direct compilation of AVD Template sources
into standalone runtime executables.

2.) XML project file output which provides both a means of saving
and exchanging your work with others, and a directly readable
source file for freely distributed runtime systems such as "guiX".

3.) A shared library will also be provided for easily connecting GUI
interfaces built by the GUI Builder (or by hand), to existing C/C++
sources, other porting efforts, scripting languages, etc.

Three runtime systems will be distributed freely to support projects
created using AVD, or constructed by hand. These three are:

1.) The shared library mentioned above.
2.) guiX, a runtime executable similar to IconX, which loads and creates
graphical interfaces on-the-fly from XML source files, and then sets
up and runs the instructions tied to each button or gadget of the interface.
3.) PrefsX, a runtime executable very close to guiX but designed to create
a manage Preference GUIs for other programs or system preferences.
The preference data itself is managed as XML data files in ENV: and ENVARC:
by using the OS's application.library (PrefsObjects API).

The current target is to release the GUI Builder for direct sale by the
end of January (2006), and to include as much of the supporting runtime
system with it at that time.

The other thing to keep in mind is that everything that the guiX and PrefsX
runtime systems will be able to do with on-the-fly generation will also be
able to be output as directly build-able C source. So, you will be able to
create guiX and PrefsX applications with no programming required, and
then use the GUI Builder to auto-generated the same functionality into
C source and a stand-alone application. This gives the developer more
freedom and should also help the novice move freely from creating simple
GUI front-ends for command line tools and such, to building more complex
and powerful applications in C.

Well that is about it for now except to mention that 2006 is going to be the
year to dig in and crank out code for OS4, and I hope my efforts will help
everyone participate in growing this great platform.

Best Regards,

Jamie Krueger

BITbyBIT Software Group LLC

_________________
Jamie Krueger
BITbyBIT Software Group LLC
jamie@bitbybitsoftwaregroup.com
PLEASE NOTE: I only speak for myself and my company,
and am not a spokesperson for Amiga Inc.

Quote:

@wegster Duh! I thought that you'd been active around here for long enough to know that you should *never* ask for an ETA of when something will be completed

Grin, naah, it just means ETAs are 'relative' rather than absolute dates

_________________
Are we not done with the same silly arguments and flames yet??!

Thanks for the update Jamie, sounds good! I wasn't expecting the final UI Builder by end of Jan, but can't complain in that respect!

Umm, although did I miss on the website or news about the piece to be worked on after the UI Builder?? (highly possible...?)

_________________
Are we not done with the same silly arguments and flames yet??!

Quote:

Umm, although did I miss on the website or news about the piece to be worked on after the UI Builder?? (highly possible...?)

Well, similar to the last time I will look to my customers for
their opinion for what is needed next.

My current thoughts are:

o Project Manager (auto-generation of Makefiles, installation
and expansion of Template sources, etc.)

o Plugin support for using CubicIDE/GoldEd, CygnusED and other
third party text editors. (For more user choices and to help
out until AVD's Text Editor is ready)

o More improvements for the SDK Browser, etc.

_________________
Jamie Krueger
BITbyBIT Software Group LLC
jamie@bitbybitsoftwaregroup.com
PLEASE NOTE: I only speak for myself and my company,
and am not a spokesperson for Amiga Inc.

Quick question: are there plans for an integrated debugger like Visual Studio or emacs+gdb?

Quote:

Quick question: are there plans for an integrated debugger like Visual Studio or emacs+gdb?

Yes, integration of a visual front end to GDB is a planned part of AVD.

AVD-Debugger Component

Best Regards,

Jamie

_________________
Jamie Krueger
BITbyBIT Software Group LLC
jamie@bitbybitsoftwaregroup.com
PLEASE NOTE: I only speak for myself and my company,
and am not a spokesperson for Amiga Inc.