Android application to manipulate sd image from the site

aaaa

aaaaa

and there is not much example of this

Welcome to RISC OS :)

For now the output of the makefile is run inside of a stronged window, but the throwback window is not activated.

There are three possible reasons why throwback doesn’t work.

 1 - Is StrongED's throwback support turned on?
     Iconbar menu > Choices.. then respond to section

 2 - Is the DDEUtils module loaded?

 3 - Is the -throwback switch specified in the compile command?

All three need to be present for throwback to work with StrongED.

2 – Is the DDEUtils module loaded?

This one has caught me out so many times, I now load it in the StrongEd !Run

aaaa

Looks interesting :)

I believe Justin Fletcher (aka Gerph) was the main driving force behind RO6 and pretty much defined what it is today and where it was going. It’s worth a read of everything on his site as he’s a very knowledgable individual both on the internal workings of RISCOS and how best to take it forward in some key areas.

I’m not sure how to say this without causing offence, but personally, I believe RISCOS development now needs to take a different approach, which is more community lead though peer review and discussion. The days of strongly willed individuals that throw their toys out the pram and override this process needs to end if we’re to take the OS forward.

I believe Justin Fletcher (aka Gerph) was the main driving force behind RO6 and pretty much defined what it is today and where it was going.

Pretty much the only programmer.

It’s worth a read of everything on his site as he’s a very knowledgable individual both on the internal workings of RISCOS and how best to take it forward in some key areas.

If you wander off onto other portions of the site and think a little about what you’re reading you get an insite into what the side effects of the OS wars included.

I’m not sure how to say this without causing offence, but personally, I believe RISCOS development now needs to take a different approach, which is more community lead though peer review and discussion. The days of strongly willed individuals that throw their toys out the pram and override this process needs to end if we’re to take the OS forward.

Fortunately the opening of the source by Castle has put the OS in a position to be community developed.
Unfortunately the strong willed element still exists and we don’t have access to all that development over t’other side of the fence.

Time for the day job.

Unfortunately the strong willed element still exists

Perhaps useful that somebody is keeping a tight rein on things or else who knows how things could spin out of control…

Pretty much the only programmer.

During my last attempt in 2012 at making some of the excellent ROL work available on the Pi. I was able to find out and talk to pretty much all of those who were programming for ROL. Whilst Justin had been the main contributor at least six other programmers had made significant contributions. Whilst a number of them were quite willing for their work to be opensourced some weren’t and as most of the work was collaborative it required all parties to agree:-(

Was there no code that could be released – it would be interesting to find out how the Viewfinder driver worked – as the card no longer works with RO5.xx :-(

Perhaps I’m misunderstanding, but presumably the ‘trump card’ in that situation would be to purchase the rights from Aaron? I assume he can do whatever he wants with the code, and any submissions to the ROL codebase would, effectively, be his property.

I’ve never used RISC OS 4+ or 6, but from the information available online, I suspect there are some useful features worth having. I appreciate that even trying to merge in (to RISC OS 5) one small feature would be a relatively large job, so even if there were no commercial difficulties, the technical ones are large enough!

Perhaps I’m misunderstanding, but presumably the ‘trump card’ in that situation would be to purchase the rights from Aaron?

When I said some of the strong willed elements still exist there was a name prominent in my mind.
Forgive and forget isn’t the first thing that comes to mind.

Perhaps I’m misunderstanding, but presumably the ‘trump card’ in that situation would be to purchase the rights from Aaron? I assume he can do whatever he wants with the code, and any submissions to the ROL codebase would, effectively, be his property.

Unfortunately not. Various problems e.g.: ROL didn’t actually have all the source code and some contributions where on a basis that didn’t give ROL full rights.
Yes in an ideal world ROL wouldn’t have done things that way but I think it was the only way they could ensure some of the later releases happened.

This sort of question comes up every few years and most times people just won’t accept what I’ve said. Please can we not have yet another rerun!

Please can we not have yet another rerun!

Definitely. Despite what people might think regarding the power of money to sway weak willed people, it isn’t going to work here.
As a born Yorkshireman I would point out that a point of principle is beyond price.

Not quite any price. But no women, no children.

That is a joke, as I have no experience or knowledge of anyone involved in this. It was a time I thankfully missed.
A great movie though!

Definitely. Despite what people might think regarding the power of money to sway weak willed people, it isn’t going to work here.
As a born Yorkshireman I would point out that a point of principle is beyond price.

I don’t think it has anything to do with being a Yorkshireman, it is more to do with whether or not one is weak-willed enough to easily compromise their morals and what they believe in by having money thrown at them.
For a while, reality TV indicated that quite a number of people would. I find this surprising, but maybe there are those who would prefer instant gratification to wishy-washy concepts like “morals”?

Of course, there is an alternative method. People who really want stuff done can post up bounties like “£2K for rounded icons”¹ and “£3K for non-native image handling integration in common formats” and… err… what else does ROLtd’s branch offer that people need?

One of two things will happen:
1. Nothing. We’ll be right where we are.
or:
2. We might start to get some of the desirable features for what may be less expensive than “the other branch” would cost (if it was theoretically possible) and nobody will have gone and poked the sleeping dragon with a stick…

But no women, no children.

Great movie. :-) :-)

as I have no experience or knowledge of anyone involved in this. It was a time I thankfully missed.

I saw the beginning and it wasn’t so pleasant. Then I went to France and we unplugged for a long time. Upon getting reconnected, I was very excited that RISC OS was going to be opened up. I was also very [upset|surprised] that the battle was still going on in some people’s minds.
I read a few posts on Drobe and the only response I had was to play The Cranberry’s song Zombie very loudly. [http://www.youtube.com/watch?v=6Ejga4kJUts if you aren’t familiar with the song]

’nuff said.

¹ I’m ever so slightly taking the p……

I’m ever so slightly taking the p……

“slightly”? I had you down as likely to shell out for not having rounded icons in the first thousand alterations. :)

Personally speaking I think JF was taking the p… or at least did it for amusement value and people took it seriously.

I read a few posts on Drobe and the only response I had was to play The Cranberry’s song Zombie very loudly.

There are a lot of people that don’t listen to the words properly or plain don’t understand that it was a protest song (like born in the USA, which ’merkins misunderstand)

“slightly”? I had you down as likely to shell out for not having rounded icons in the first thousand alterations. :)

Well, yeah, there is that.

There are a lot of people that don’t listen to the words properly or plain don’t understand that it was a protest song

There are those who can’t get past the singer’s accent, don’t know much/anything about The Troubles and don’t know about the two boys killed in ’93, so they think the song is something about zombies (the Romero kind). <sigh>
But some of the lyrics are quite apt for the above situation as well…

aaaa

aaaaa

seems more to have a user based point of view, to correct superficial things, rather than truly architectural design

I see this a lot in my day job, where I take over IT divisions / big IT projects and sort this kind of issue out, particularly where people are micro managing or simply not focusing on their specific role. In my experience, the longer a person is in a role – the more they drift and the less focused they become. More often than not I have to walk them as they’re either no longer suitable, interfere in other areas or simply block progress as they get set in their ways. I don’t particularly like ruining peoples careers, but at the end of the day I’ve been called in from the highest level to sort out major business problems, so the long term goal has to take precedence. More often than not, it’s the long term goal that gets lost whilst people focus in trivial issues as you point out.

Anyhow, I digress. Yes, lots of interesting ideas on his site. How much of it is still applicable I don’t know.

RISCOS 5 doesn’t seem to have a long term goal at the moment (not clearly defined and documented at any rate), there’s lots of additions going on to add support for new chips and SoC features and daily maintenance to resolve bugs etc, but nothing I would call long-term.

If you look at the threads on multi-core / multi-threading, they’ve been running for years, but as far as I can tell nobody has thought to build a project plan on how to achieve them. Looking at them as an overall task, they’re near impossible but broken down into a detailed project with hundreds of smaller tasks, they’re all pretty trivial to implement.

The root problem here is that next to nobody understands the RISCOS source and it doesn’t contain enough documentation within the code to easily work out what’s involved. The first step should be fully documenting the code and public interfaces (SWI’s etc) and build flow diagrams showing interdependencies. This needs to be done under an SPSS / QA type framework so analysis of code changes can be performed and test plans built following all code changes.

Another thing I feel should happen is peer-review of all code changes and immediate rejection if there’s not enough documentation. I’d expect to see every other line of code have a comment so you can read what’s going on in English and not have to decode registers etc. The simple rule here is, if your mother can’t follow it – you’ve not documented it enough!

aaaa

The root problem here is that next to nobody understands the RISCOS source and it doesn’t contain enough documentation within the code to easily work out what’s involved. The first step should be fully documenting the code and public interfaces (SWI’s etc) and build flow diagrams showing interdependencies.

I’d agree with this. I’m a Software Engineer, and used to use RISC OS an awful lot. But I only ever dabbled in BASIC and some very simple C/OSLib/Toolbox. In principle, I’m sure I could pick-up the low-level detail, but I can’t imagine where to start. Maybe I just need to read the PRMs cover-to-cover? I assumed they were a reference, not a walkthrough.

Another thing I feel should happen is peer-review of all code changes and immediate rejection if there’s not enough documentation. I’d expect to see every other line of code have a comment so you can read what’s going on in English and not have to decode registers etc. The simple rule here is, if your mother can’t follow it – you’ve not documented it enough!

Absolutely. Code reviews are standard practice at work, and you don’t need to understand the detail 100%. It should make sense to a power-user or general developer.

aaaa