@AlexC

Quote:

Gdb doesn't work too well, at least here it crashes easily

Read here and down from there


@Jamie
Welcome back to "our" side of AmigaOS

Last edited by elwood on 07-Sep-2010 at 03:33 PM.

_________________
Philippe 'Elwood' Ferrucci
Sam460 1.10 Ghz
AmigaOS 4 betatester
Amiga Translator Organisation

@AlexC

Thanks AlexC,

I am happy to hear that you find the SDK Browser useful,
what version are you currently running, and under which
release/update of OS4/4.1?

I'm not sure what you mean about the AVD Template being
to "unix*ish" and not "amiga*ish* enough, maybe it's the
layered structure? (which evolved from writing cross platform
software) Anyway, the AVD Template is loaded with Amiga
specific features, from List handling to setting itself up as
a commodity.

@All

Thanks for the tips on getting up to speed with the OS/SDK
updates, I am working on that now. After which I will be retesting
both my current build of the AVD Suite and the currently public
version against AmigaOS4.1 Update2.

Question, is everyone out there running OS4.1u2, or are
there still users running on AmigaOS4.0?

Best Regards,

Jamie Krueger

_________________
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.

@JamieKrueger

I'm running OS4.1u2, but I do know of several users still running 4.0. Glad to see you back...

_________________
--
-=#Val#=-
Valiant@Camelot


Amiga 1000; Amiga 2000; Amiga 3000T; CD-TV; CD32;
AmigaOne-XE 800Mhz G4;Sam400ep 666Mhz;
AmigaOne X-1000 1.8Ghz PA6T-1682M

@elwood

Thanks for the link, will try this one with ggdb and from the Grim Reaper with "Attach to gdb".

_________________
AlexC's free OS4 software collection

AmigaOne XE/X1000/X5000/UAE-PPC OS4 laptop/X-10 Home Automation

@JamieKrueger

I'm using version 1.6.0.0 of SDK browser as the last registered release was 1.5.x.x if I'm not mistaken.

On the OS side I'm running 4.1 beta so it's partly newer than 4.1u2.

As for the "unix'ish" aspects, I had a long list back then when it came out but didn't want to bother you with unimportant stuff like that.

It's been so long that I can't remember what my gripes were but I have a vague recollection that it had something to do with not using standard amiga version numbering schemes, menus, args templates, and/or stuff like that.

I'm really not sure anymore so once you get the ball rolling again I'll start from scratch and will let you know as/if I run into such things.

_________________
AlexC's free OS4 software collection

AmigaOne XE/X1000/X5000/UAE-PPC OS4 laptop/X-10 Home Automation

@JamieKrueger

Quote:

Question, is everyone out there running OS4.1u2, or are there still users running on AmigaOS4.0?

I believe that OS4 for Classic machines+PPC cards was left at 4.0 version.

_________________
All glory to the Hypnotoad!

@JamieKrueger
Sometimes, a great programmer coming back is way better news than anything else we're hearing as of late

_________________
SamFlex Complete 800Mhz System + AmigaOS 4.1 Update 4
Amiga 2000 DKB 2MB ChipRam GVP G-Force040 Picasso 2 OS3.9 BB2
AmigaCD 32

@billt

im not sure if i can speak for someone else, but i feel like by this time os4 classic users have accepted to be left behind. i for myself switched back to os3 and turn 4.0 only occassionaly to test some piece of software, or compare another compile.
i think it has been pushed too far already, so move on, who wants os4.1 will switch to a new machine. im fine with it.

Last edited by wawa on 08-Sep-2010 at 04:31 PM.
Last edited by wawa on 08-Sep-2010 at 02:33 PM.

@wawa

Yes, everybody should run OS4.1 update2 by now.

I have older versions of OS4 on my harddisk and i can boot
them all, but since update 2 i have not returned to those partitions.

_________________
A1G3-SE + OS4.1 u1 iso (x2)

@JamieKrueger
Quote:

Question, is everyone out there running OS4.1u2, or are there still users running on AmigaOS4.0?

You should target Amiga OS 4.1 which will soon have two new Amiga hardware platforms added: Sam460ex and AmigaOne X1000.

Welcome back!

_________________
ExecSG Team Lead

@JamieKrueger

Hello,
i restart with programming for the amiga4.x and your tool sdk-browser is very useful. it makes it much easier to find back in this hobby since my amiga 3.x days.
it is running without any problem under 4.1u2.
thank you for this nice software!

_________________
Sam460ex, Sam667Flex, CDTV, A600 und CD32
Amiga User since 1987

@All

My goal is always to retain backward compatibility whenever
possible. However, given that AVD is a development system
meant to be used to author software for the future of AmigaOS
based machines first and foremost, I agree that the focus
should be to run on and write for AmigaOS4.1u2 first.

Despite this AVD will still require the ability to support targeting
older versions of AmigaOS as new releases and their respective
SDKs emerge. Even if AVD itself might require the latest greatest
AmigaOS to run, it should still retain the ability to target older
versions of the OS. At least within reason.

Ideally, everyone with a machine should be running to newest
OS version all the times, and all new development should target
that newest release. However, this does not always happen.
And there are times when you really need to be able to build
a new piece of software for an older version of the OS. The long
history of AmigaOS emulation is easily proof of that.

Thanks everyone for your input, please keep it coming.

Best Regards,

Jamie Krueger

_________________
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.

@AlexC

Quote:

AlexC wrote: @JamieKrueger I'm using version 1.6.0.0 of SDK browser as the last registered release was 1.5.x.x if I'm not mistaken. On the OS side I'm running 4.1 beta so it's partly newer than 4.1u2.

My current build of the SDK Browser is v1.8.0.141.
After I have a chance to test it against AmigaOS4.1u2 I plan to make
a new release. This version is slated to become v2.0, and contains
several new features over the v1.6 version, like:

o Structure browsing

o More extended hyperlink usage (double-click on function names,
include statements, etc. in any text and jump directly to where it's
defined - or double-click on a word and have it automatically placed
in the search line).

o Extended search features; Search for files within a given directory,
and even search within the search results to filter down the list.

o Mouse scroll-wheel acceleration option (when using the scroll wheel
over either the list or the display areas, the speed of the line/page movement
is based on the accumulated speed of the mouse's scroll wheel. So
the faster you wheel, the faster the page will scroll). To really see
what this feature does for you, just try wheeling down the "Commands"
list of 2170+ API functions, and then disable acceleration via the menu
option and try again. :)

o Load an external file or perform a lookup operation within the SDK Browser
from an external program using either a CLI or Arexx script call.

o Easier Public Screen handing.

o And several more little improvements I can think of right now.


Quote:

As for the "unix'ish" aspects, I had a long list back then when it came out but didn't want to bother you with unimportant stuff like that. It's been so long that I can't remember what my gripes were but I have a vague recollection that it had something to do with not using standard amiga version numbering schemes, menus, args templates, and/or stuff like that. I'm really not sure anymore so once you get the ball rolling again I'll start from scratch and will let you know as/if I run into such things.

Sure, I can see that. This first AVD template does provide more of a UNIX style command line
interface that is true (but also easy to replace). The use of a four position version numbering
system (Major.Minor.Maintenance.Build) and the automated version numbering tool that
goes with it (Increment_Version), is required for me to keep an accurate track of all development,
release, and bug fixes within a given release. I provided this within the AVD Template because
I felt others would benefit from the same.

While traditionally we see two position (Major.Minor) version numbers within AmigaOS
applications, my thoughts are this system should be enhanced. However, it is a simple
matter to only display the Major.Minor part of a software release, and I plan to support
AmigaOS style versioning within AVD either way. As I equally plan to make AVD Template
features, more customizable as well.

Best Regards,

Jamie Krueger

_________________
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:

DAX wrote: @JamieKrueger Sometimes, a great programmer coming back is way better news than anything else we're hearing as of late

+1 welcome back

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

@JamieKrueger

Welcome back Jamie, in our small community it's always good news to gain a skilled programmer as you.

I am not using SDKBrowser during my own devs, I vaguely remember having tried it but I already had my habits with AutodocViewer and the CubicIDE own solution. May it forth a new try

However I was really interested in your tool to build GUI, reviews I read at the time (AmiWest 2008?) were really promising.

If you really want something that might allow you to earn some bits of money I would say that either a GDB GUI either a fully separate debugger would be the way to go given the target price is reasonable (I would say for myself a price between 20 and 30 euros would be, and if you think the price is low compared to the investment, think about the fact that if you follow correctly the product you can easily start with a small working thing, and after that deliver paying upgrades for around 10 euros).

Good luck and again welcome back !!!

_________________
AOS 4.1 : I dream it, Hyperion did it !
Now dreaming AOS 4.2...
Thank you to all devs involved for this great job !

@abalaban

I agree. AOS4 desperately lacks good debugging tools.
The reason why there's still no proper Pagestream 5 release for AOS4 is,
that Daron can't debug his software appropriately (and in the way he's used
to do on other platforms -- at least according to his statements on the PageStreamAmigaBeta-Mailinglist).

So, a good debugging environment and a gui builder would be very appreciated

regards,
nexus

Last edited by nexus on 09-Sep-2010 at 09:05 AM.

_________________
dye 'em black!

@JamieKrueger

Quote:

This version is slated to become v2.0, and contains several new features over the v1.6 version, like:

Looks sweet

Quote:

The use of a four position version numbering system (Major.Minor.Maintenance.Build) and the automated version numbering tool that goes with it (Increment_Version), is required for me to keep an accurate track of all development

Where i work (as a Windows developer) we use a 4 position version numbering scheme and i'm used to it, i find it very useful... to be honest i find the Amiga way a bit strange instead

I'm really looking forward for your new tools, i've always considered AVD a must-have on OS4 and one of the first products i'd buy once released (sadly i didn't have the possibility to subscribe back then, it was tough times for me).
Thanks for coming back

Edit: have you ever thought about joining forces with the Codebench project? You have great tools on your part, you could provide the SDK browser + code templates/wizards + GUI builder + debugger which are invaluable tools and use Codebench as code editor + project management (as far as i can tell from demos and screenshots it seems to me that those are the points where each is positioned better than the other). I believe it would be a killer combo!!

Last edited by Nibunnoichi on 09-Sep-2010 at 09:19 AM.

_________________
Proud Amigan since 1987
Owner of various Commodore and a SAM440ep\OS4.1FE
See them on http://retro.furinkan.org/

Yehaa! Now i have too found the installer script i made for the AVD-progs

_________________

@JamieKrueger:

Quote:

are there still users running on AmigaOS4.0?

Me, albeit only occassionally.

Do most of my work on a Mac these days.

_________________
Robert
--
A1XE G4, OS4.1. Peg1 G3, MOS 1.4.
Abel Soul - Check out our tunes on Spotify

@All

One of the goals of AVD is to be a highly integrated environment,
with all components able to freely communicate with each other
in order to either invoke the display of a given component, or even
call upon that component to perform a function and return the
result.

This system is currently built upon an AmigaOS specific internal
message passing mechanism. It provides the very efficient, direct
means of communications needed to tie multiple applications
together as one.

In a similar way, Arexx has been used for years to connect independent
Amiga applications together via external scripting. I still remember
the days of using Arexx scripts to allow programs like DPaint and ADPro
to work together. At one point I even wrote an extensive Arexx script
for CygunED that built and assembled a software distribution CDROM
from code compiled on 14 different UNIX boxes. Arexx directed to remote
complies, pulled the resulting files over to my A4000T and burned them
out to CDROM via MasterISO. All from the press of one function key.

The point being, I believe in the AmigaOS way of applications that are
open enough to give their users the freedom to work how they want,
and with what they want. Therefore you can expect to see AVD's internal
communications system extended to provide a public "API" to the system
so that every component can be access or controlled externally. It has
also been my goal that AVD will allow it's users to work with any part
of the system they choose, while simultaneously aiding working with
external applications.

The SDK Browser (upcoming v2.0 release) already supports being invoked
from external editors, etc. via both a CLI and Arexx interface. This is only
the beginning.

On another note, since the SDK Browser is already reaching v2.0, my
focus will be on the development of the GUI Builder and Debugger
components next. I see the Debugger project as having two distinct
parts; A graphical interface to GDB, for binary level debugging, and
a Source Level Debugger, for pre-compile source level debugging.
The later with have heavy ties to the Text Editor component, either
AVD's or a third party editor via Arexx/CLI.

Best Regards,

Jamie Krueger

_________________
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.