Page 1 of 2

SDK 2017 wishes

PostPosted: Sat Jul 01, 2017 2:12 pm
by capehill

Re: SDK 2017 wishes

PostPosted: Sat Jul 01, 2017 10:11 pm
by Spektro
Hello,
Here is a list of tools I would like to see included in the next SDK:

  • CodeBench
  • SDK Browser
  • revision control system
  • tool for magnifying and examining individual pixels on the screen
  • tool for splitting large files
  • tool for editing and viewing binary files
  • binary file patcher
  • binary file to C source code converter
  • C/C++ source code formatter
  • audio programming language Csound

Re: SDK 2017 wishes

PostPosted: Sun Jul 02, 2017 1:54 pm
by chris
As mentioned in other threads, some DT descriptor creator. Even the old 68k dtdesc would do for now.

Re: SDK 2017 wishes

PostPosted: Sun Jul 02, 2017 6:27 pm
by mritter0
The complete source code to button.gadget so we can start to build our own classes. Make file, docs, the works.

Re: SDK 2017 wishes

PostPosted: Sun Jul 02, 2017 8:45 pm
by broadblues
mritter0 wrote:The complete source code to button.gadget so we can start to build our own classes. Make file, docs, the works.


I don't think button.gadget would make good example, despite it's apparent simplicity ('just' a button) it's one of the more complex gadgets, but I do agree that it would beneficial to have a simple yet complete gadget example.

Re: SDK 2017 wishes

PostPosted: Mon Jul 03, 2017 11:26 am
by capehill
Personally I have been using Cmake recently. It has a couple of issues (no stack cookie and then some link issue with libDL IIRC) but they can be worked around easily. http://os4depot.net/index.php?function= ... /cmake.lha

Re: SDK 2017 wishes

PostPosted: Tue Jul 04, 2017 10:40 am
by Belxjander
Would submissin examples be allowable as part of "Community Contributin"s ?

As I can provide a *minimal* and *working* DataType template (currently I would only need to strip out some project specific code that is not essential to DataTypes operations...and this would also double as a working BOOPSI class example as well

as DataTypes are a "superset" expanding on gadget classes afaik...

Would this help?

P.S.: ThomasRapp recommended the "MakeDT-1.3" package for DataTypes Descriptors building...
the updated version actually works extremely well and is ARexx scripts.
This would solve the whole DT Descriptors build requirements if it can be included quite wonderfully too.

Re: SDK 2017 wishes

PostPosted: Tue Jul 04, 2017 2:17 pm
by trixie
@Belxjander

Would submissin examples be allowable as part of "Community Contributin"s?

You can always send your example code or tutorials for inclusion in the AmigaOS Developer Wiki. I'll be happy to post the material for you.

Re: SDK 2017 wishes

PostPosted: Wed Jul 05, 2017 12:09 am
by Belxjander
Spektro wrote:Hello,
Here is a list of tools I would like to see included in the next SDK:

  • CodeBench
  • SDK Browser
  • revision control system
  • tool for magnifying and examining individual pixels on the screen
  • tool for splitting large files
  • tool for editing and viewing binary files
  • binary file patcher
  • binary file to C source code converter
  • C/C++ source code formatter
  • audio programming language Csound


Multiview with AROS binary.datatype port provides Hex and Text display of arbitrary data not otherwise recognised.

I think a "Hexeditor" could be modified from that? or at least provide an "offset&block" edit approach which can be reflected back to the source object with saving it.

I'm in the middle of making several other DataTypes and have the Enhancer pack with both Multiview & Multiviewer for testing which appears to work very well for what I have so far (which actually requires some of my DataTypes to recursibely self-expand their own DataType decode and linking additional objects from disk...)

EDIT: +http://os4depot.net/?function=showfile&file=development/example/template.lha
for anyone to use as they see fit...has a couple of extra details...those will need to be cut out or changed.

Full BOOPSI class in a Library (multiple extra interfaces too... not actually needed but hell... it's an example...)
for anyone to look at / read / modify or generally abuse into something useful.
just lacks any 680x0 specific backwards compatability details. see the automated skeleton builder for those.


I *might* be able to do something about patching and other "quick" console tools as well very quickly...
I'll see what time I have this week as I can't promise anything quick until maybe the 9th, as long as it takes me less than a few hours and not like my other projects which require some strange things not 100% OS compliant but workable design items.

EDIT: Had less time than I originally planned, with a couple of 30+ hour days... crashing out mid-task is no fun.

Re: SDK 2017 wishes

PostPosted: Wed Jul 05, 2017 11:07 pm
by kas1e
@Belxander
After all those years of your cheap talking without delivering things, you still continue to talk in the same way as before. Facepalm on you! Same good old Belxander style.

@Spectro
You make it sound like there is a lot developers who just wait "wishes" to just write a lot of new tools :) I mean, you for sure realise that new SDK it will be just mostly ADTOOLS build of newer gcc (on which Sebastian works), as well as just "some" updated components like make, clib (which was in develop for years as well, just latest one will be included) ? I mean its not like there is many programmers who works hard on SDK to deliver new utilities with, it will be mostly updated SDK, nothing uber new in.

As for your whole list:
CodeBench - property of Simon, maybe will be in sold someday
SDK Browser - property of Jamie, which in sold. And there is another one, mui mased: minad
Tool for magnifying and examining individual pixels on the screen - not what should be in SDK, its just 3d party help code which developers should do ourself.
tool for splitting large files - that also not for SDK. And probably SPLIT/JOIN should work ?
tool for editing and viewing binary files - there a lot to choice already, even i port one some years ago: zaphod
binary file patcher - already presend everywhere called PATCH
binary file to C source code converter - that not _that_ easy. Its almost unpossible to make from binary file normal loking or even working C code. That doesn't not matter on what platform is it. There is disassemblers (on any platform), which can disassemble for you from binary to machine code (assembler), and even on os4 you can do it (by objdump for example), but then its still assembly code which you need to rewrtie to C manually. That like this on any platform.