Apple's current status with their development site illustrates just one of the many issues with walled gardens. The most significant of which is the compromise if user freedoms. The one illustrated by last weeks incident shows us just how much developers for the iPhone and Mac app stores are at Apple's mercy. While this was inherently obvious it has never been more obvious than right now just how fragile this relationship always was.
The real evil of Apple's app store is not the app store itself, but the code signing technology that is tied to it. Since Apple is the only entity which can approve binaries to run on iOS devices or to go into the iOS or Mac app stores it represents a single point of failure. This is the true evil of it. What happens if Apple goes away? We're left with devices which can't be used since the mothership is now gone. Is this right?
I only hope that this incident gives people who are enamored with this concept time to reflect on what it's weaknesses really are.
Google has managed to implement an appstore without much of the evil that is inherent in Apple's implementation and, even though Google may have done some evil with the NSA, at least it didn't do quite as much evil as Apple did in this particular instance.
Wednesday, July 24, 2013
Saturday, June 15, 2013
GNUstep Mythbusting...
Myth #1: GNUstep doesn't care about or implement any of the Cocoa frameworks or classes
As illustrated by some of the comments here, people still don't understand, really, what GNUstep is all about. Sometimes I think it's the name, and sometimes I think it's just that people are willfully ignoring the facts or just want to spew nonsense in order to sound intelligent.
GNUstep implements most of the 10.5 APIs and is currently working on some of the 10.6, 7 and 8 Cocoa APIs. Additionally, the project has implemented CoreFoundation, CoreGraphics and CoreAnimation is upcoming. So, please, people. Get off of this whole "GNUstep doesn't care" thing. We care and we are implementing as much as we can. We are roughly 20 individuals, Apple is multi-billion dollar corporation.
Myth #2: No one uses GNUstep.
Wrong again, GNUstep is currently in use in millions of devices around the world. This company http://www.apportable.com is using much of the GNUstep codebase to accomplish this. It forms the basis for their UIKit implementation which is used to port applications from iOS to Android. If we were only OpenStep, this wouldn't be possible. Additionally, GNUstep is used by a number of companies to produce ports of their applications to Windows and to Linux. See our wiki page about GNUstep success stories for more.
Myth #3: GNUstep can only look like NeXTSTEP
Not true. GNUstep has devoted a lot of time to theming and the ability to make applications written using GNUstep look like just about anything you would like them to look like.
I'm sure these aren't the only myths circulating, but they are the most prominent and, to me, the most annoying. I can't seem to get it through people's heads. GNUstep is so much more than it used to be and so much more than people think it is. I wish, for once, that people would actually look at the project before making judgements.
Myth #4: GNUstep looks like NeXTSTEP, so it must only implement NeXTSTEP
I honestly never expected developers to judge a book by it's cover, but many people do, even otherwise intelligent people.
As illustrated by some of the comments here, people still don't understand, really, what GNUstep is all about. Sometimes I think it's the name, and sometimes I think it's just that people are willfully ignoring the facts or just want to spew nonsense in order to sound intelligent.
GNUstep implements most of the 10.5 APIs and is currently working on some of the 10.6, 7 and 8 Cocoa APIs. Additionally, the project has implemented CoreFoundation, CoreGraphics and CoreAnimation is upcoming. So, please, people. Get off of this whole "GNUstep doesn't care" thing. We care and we are implementing as much as we can. We are roughly 20 individuals, Apple is multi-billion dollar corporation.
Myth #2: No one uses GNUstep.
Wrong again, GNUstep is currently in use in millions of devices around the world. This company http://www.apportable.com is using much of the GNUstep codebase to accomplish this. It forms the basis for their UIKit implementation which is used to port applications from iOS to Android. If we were only OpenStep, this wouldn't be possible. Additionally, GNUstep is used by a number of companies to produce ports of their applications to Windows and to Linux. See our wiki page about GNUstep success stories for more.
Myth #3: GNUstep can only look like NeXTSTEP
Not true. GNUstep has devoted a lot of time to theming and the ability to make applications written using GNUstep look like just about anything you would like them to look like.
I'm sure these aren't the only myths circulating, but they are the most prominent and, to me, the most annoying. I can't seem to get it through people's heads. GNUstep is so much more than it used to be and so much more than people think it is. I wish, for once, that people would actually look at the project before making judgements.
Myth #4: GNUstep looks like NeXTSTEP, so it must only implement NeXTSTEP
I honestly never expected developers to judge a book by it's cover, but many people do, even otherwise intelligent people.
Sunday, April 14, 2013
This is version 1.2.20 of Gorm.
1 ANNOUNCE
**********
This is version 1.2.20 of Gorm.
1.1 What is Gorm?
=================
Gorm is an acronym for Graphic Object Relationship modeler (or perhaps
GNUstep Object Relationship Modeler).
Gorm is a clone of the Cocoa (OpenStep/NeXTSTEP) `Interface Builder'
application for GNUstep.
1.2 Noteworthy changes in version `1.2.20'
==========================================
* Bug fixes #28643, #32827
* Corrected issues with updating document when there is a change.
* Add cells as objects to the document so they can be properly
edited.
* Changes to prevent recursive frame change notifications.
1.3 How can I get support for this software?
============================================
You may wish to use the GNUstep discussion mailing list for general
questions and discussion. Look at the GNUstep Web Pages for more
information regarding GNUstep resources `http://www.gnustep.org/'
1.4 Where can you get it? How can you compile it?
==================================================
You can download sources and rpms (for some machines) from
`ftp://ftp.gnustep.org/pub/gnustep/dev-apps'.
1.5 Where do I send bug reports?
================================
Bug reports can be sent to
1.6 Obtaining GNU Software
==========================
Check out the GNUstep web site. (`http://www.gnustep.org/'), and the
GNU web site. (`http://www.gnu.org/')
Tuesday, April 02, 2013
Version 0.23.1 of the GNUstep GUI library (`gnustep-gui') is available
1 ANNOUNCE
**********
This is version 0.23.1 of the GNUstep GUI library (`gnustep-gui').
1.1 What is the GNUstep GUI Library?
==============================
It is a library of graphical user interface classes written completely
in the Objective-C language; the classes are based upon Apple's Cocoa
framework (which came from the OpenStep specification as release by
NeXT Software, Inc). The library has been enhanced in a number of ways
to take advantage of the GNU system. These classes include graphical
objects such as buttons, text fields, popup lists, browser lists, and
windows; there are also many associated classes for handling events,
colors, fonts, pasteboards and images.
The GNUstep GUI Library is designed in two parts. The first part is
the front-end component which is independent of platform and display
system. This front-end is combined with a back-end component which
handles all of the display system dependent such as specific calls to
X/Windows. This design allows the GNUstep applications to have the
"look and feel" of the underlying display system without any changes to
the application, and the library can be easily ported to other display
systems.
The GNUstep GUI Library requires the GNU Objective-C compiler, the
GNUstep Base Library, the TIFF Graphics library, and a back-end
component like the GNUstep 'Back' Backend.
1.2 Noteworthy changes in version `0.23.1'
==============================
This is a bugfix release, primarily to deal with coding/archiving
issues.
1.3 Where can you get it? How can you compile it?
==============================
The gstep-gui-0.23.1.tar.gz distribution file has been placed at
`ftp://ftp.gnustep.org/pub/
Read the INSTALL file or the GNUstep-HOWTO for installation
instructions.
1.4 Where do I send bug reports?
==============================
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
1.5 Obtaining GNU Software
==========================
Check out the GNUstep web site. (`http://www.gnustep.org/'), and the
GNU web site. (`http://www.gnu.org/')
**********
This is version 0.23.1 of the GNUstep GUI library (`gnustep-gui').
1.1 What is the GNUstep GUI Library?
==============================
It is a library of graphical user interface classes written completely
in the Objective-C language; the classes are based upon Apple's Cocoa
framework (which came from the OpenStep specification as release by
NeXT Software, Inc). The library has been enhanced in a number of ways
to take advantage of the GNU system. These classes include graphical
objects such as buttons, text fields, popup lists, browser lists, and
windows; there are also many associated classes for handling events,
colors, fonts, pasteboards and images.
The GNUstep GUI Library is designed in two parts. The first part is
the front-end component which is independent of platform and display
system. This front-end is combined with a back-end component which
handles all of the display system dependent such as specific calls to
X/Windows. This design allows the GNUstep applications to have the
"look and feel" of the underlying display system without any changes to
the application, and the library can be easily ported to other display
systems.
The GNUstep GUI Library requires the GNU Objective-C compiler, the
GNUstep Base Library, the TIFF Graphics library, and a back-end
component like the GNUstep 'Back' Backend.
1.2 Noteworthy changes in version `0.23.1'
==============================
This is a bugfix release, primarily to deal with coding/archiving
issues.
1.3 Where can you get it? How can you compile it?
==============================
`ftp://ftp.gnustep.org/pub/
Read the INSTALL file or the GNUstep-HOWTO for installation
instructions.
1.4 Where do I send bug reports?
==============================
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
==========================
Check out the GNUstep web site. (`http://www.gnustep.org/'), and the
GNU web site. (`http://www.gnu.org/')
The GNUstep Base Library, version 1.24.4, is now available.
1 Announcement
**************
The GNUstep Base Library, version 1.24.4, is now available.
1.1 What is the GNUstep Base Library?
==============================
The GNUstep Base Library is a library of general-purpose, non-graphical
Objective C objects. For example, it includes classes for strings,
object collections, byte streams, typed coders, invocations,
notifications, notification dispatchers, moments in time, network ports,
remote object messaging support (distributed objects), and event loops.
It provides functionality that aims to implement the non-graphical
portion of the OpenStep standard (the Foundation library).
There is more information available at the GNUstep homepage at
`http://www.gnustep.org'.
1.2 Noteworthy changes in version `1.24.4'
==============================
* Updated time zone data
* OSX 10.7 NSCalendar methods
* Portability improvments and minor bugfixes
* More testcases in the testsuite
1.3 Where can you get it? How can you compile it?
==============================
The gnustep-base-1.24.4.tar.gz distribution file has been placed at
`ftp://ftp.gnustep.org/pub/
**************
The GNUstep Base Library, version 1.24.4, is now available.
1.1 What is the GNUstep Base Library?
==============================
The GNUstep Base Library is a library of general-purpose, non-graphical
Objective C objects. For example, it includes classes for strings,
object collections, byte streams, typed coders, invocations,
notifications, notification dispatchers, moments in time, network ports,
remote object messaging support (distributed objects), and event loops.
It provides functionality that aims to implement the non-graphical
portion of the OpenStep standard (the Foundation library).
There is more information available at the GNUstep homepage at
`http://www.gnustep.org'.
1.2 Noteworthy changes in version `1.24.4'
==============================
* Updated time zone data
* OSX 10.7 NSCalendar methods
* Portability improvments and minor bugfixes
* More testcases in the testsuite
1.3 Where can you get it? How can you compile it?
==============================
The gnustep-base-1.24.4.tar.gz distribution file has been placed at
`ftp://ftp.gnustep.org/pub/
The GNUstep Makefile Package version 2.6.4 is now available.
1 Announcement
**************
The GNUstep Makefile Package version 2.6.4 is now available.
1.1 What is the GNUstep makefile package?
==============================
The makefile package is a simple, powerful and extensible way to write
makefiles for a GNUstep-based project. It allows the user to write a
project without having to deal with the complex issues associated with
configuration, building, installation, and packaging. It also allows
the user to easily create cross-compiled binaries.
1.2 Changes in version `2.6.4'
==============================
Test framework extended equality tests.
Android build target
1.3 Obtaining gnustep-make
==========================
You can get the gstep-make-2.6.4.tar.gz distribution file at
`ftp://ftp.gnustep.org/pub/
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
**************
The GNUstep Makefile Package version 2.6.4 is now available.
1.1 What is the GNUstep makefile package?
==============================
The makefile package is a simple, powerful and extensible way to write
makefiles for a GNUstep-based project. It allows the user to write a
project without having to deal with the complex issues associated with
configuration, building, installation, and packaging. It also allows
the user to easily create cross-compiled binaries.
1.2 Changes in version `2.6.4'
==============================
Test framework extended equality tests.
Android build target
1.3 Obtaining gnustep-make
==========================
You can get the gstep-make-2.6.4.tar.gz distribution file at
`ftp://ftp.gnustep.org/pub/
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
Monday, March 04, 2013
Viking by Brilliant Service is using GNUstep in the Objective-C based software for their Head Mounted Device, pictured here:
Their website is here. :) I'm very happy to see GNUstep being used in so many new and different places. The prospects for the future are exciting.
Their website is here. :) I'm very happy to see GNUstep being used in so many new and different places. The prospects for the future are exciting.
Sunday, March 03, 2013
The GNUstep Base Library, version 1.24.3, is now available.
1 Announcement
**************
The GNUstep Base Library, version 1.24.3, is now available.
1.1 What is the GNUstep Base Library?
==============================
The GNUstep Base Library is a library of general-purpose, non-graphical
Objective C objects. For example, it includes classes for strings,
object collections, byte streams, typed coders, invocations,
notifications, notification dispatchers, moments in time, network ports,
remote object messaging support (distributed objects), and event loops.
It provides functionality that aims to implement the non-graphical
portion of the OpenStep standard (the Foundation library).
There is more information available at the GNUstephomepage at
`http://www.gnustep.org'.
1.2 Noteworthy changes in version `1.24.3'
==============================
* Implementation of the NSXML DOM classes
* Implementation of consistent TLS/SSL support
* Implementation of new/selectable sorting algorithms
* More explicit dependencies on external libraries.
1.3 Where can you get it? How can you compile it?
==============================
The gnustep-base-1.24.3.tar.gz distribution file has been placed at
`ftp://ftp.gnustep.org/pub/
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
**************
The GNUstep Base Library, version 1.24.3, is now available.
1.1 What is the GNUstep Base Library?
==============================
The GNUstep Base Library is a library of general-purpose, non-graphical
Objective C objects. For example, it includes classes for strings,
object collections, byte streams, typed coders, invocations,
notifications, notification dispatchers, moments in time, network ports,
remote object messaging support (distributed objects), and event loops.
It provides functionality that aims to implement the non-graphical
portion of the OpenStep standard (the Foundation library).
There is more information available at the GNUstephomepage at
`http://www.gnustep.org'.
1.2 Noteworthy changes in version `1.24.3'
==============================
* Implementation of the NSXML DOM classes
* Implementation of consistent TLS/SSL support
* Implementation of new/selectable sorting algorithms
* More explicit dependencies on external libraries.
1.3 Where can you get it? How can you compile it?
==============================
The gnustep-base-1.24.3.tar.gz distribution file has been placed at
`ftp://ftp.gnustep.org/pub/
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
GNUstep GUI 0.23.0
1 ANNOUNCE
**********
This is version 0.23.0 of the GNUstep GUI library (`gnustep-gui').
1.1 What is the GNUstep GUI Library?
==============================
It is a library of graphical user interface classes written completely
in the Objective-C language; the classes are based upon Apple's Cocoa
framework (which came from the OpenStep specification as release by
NeXT Software, Inc). The library has been enhanced in a number of ways
to take advantage of the GNU system. These classes include graphical
objects such as buttons, text fields, popup lists, browser lists, and
windows; there are also many associated classes for handling events,
colors, fonts, pasteboards and images.
The GNUstep GUI Library is designed in two parts. The first part is
the front-end component which is independent of platform and display
system. This front-end is combined with a back-end component which
handles all of the display system dependent such as specific calls to
X/Windows. This design allows the GNUstep applications to have the
"look and feel" of the underlying display system without any changes to
the application, and the library can be easily ported to other display
systems.
The GNUstep GUI Library requires the GNU Objective-C compiler, the
GNUstep Base Library, the TIFF Graphics library, and a back-end
component like the GNUstep 'Back' Backend.
1.2 Noteworthy changes in version `0.22.0'
==============================
New features include:
* This version is binary incompatible with previous versions due to
the change of NSNotFound in GNUstep base.
* Support for drawing the GUI with a scale factor, for high-DPI
monitors.
* Character panel
* Color picker "Magnifier" tool, for grabbing the color of arbitrary
parts of the screen
Many NSImage improvements (Mac OS X 10.6 drawing methods, better
selection of image reps, better support for icons). Many bugfixes,
including in Xib loading, printing, and NSView geometry.
1.3 Where can you get it? How can you compile it?
==============================
The gstep-gui-0.23.0.tar.gz distribution file has been placed at
`ftp://ftp.gnustep.org/pub/
Read the INSTALL file or the GNUstep-HOWTO for installation
instructions.
1.4 Where do I send bug reports?
==============================
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
1.5 Obtaining GNU Software
==========================
Check out the GNUstep web site. (`http://www.gnustep.org/'), and the
GNU web site. (`http://www.gnu.org/')
**********
This is version 0.23.0 of the GNUstep GUI library (`gnustep-gui').
1.1 What is the GNUstep GUI Library?
==============================
It is a library of graphical user interface classes written completely
in the Objective-C language; the classes are based upon Apple's Cocoa
framework (which came from the OpenStep specification as release by
NeXT Software, Inc). The library has been enhanced in a number of ways
to take advantage of the GNU system. These classes include graphical
objects such as buttons, text fields, popup lists, browser lists, and
windows; there are also many associated classes for handling events,
colors, fonts, pasteboards and images.
The GNUstep GUI Library is designed in two parts. The first part is
the front-end component which is independent of platform and display
system. This front-end is combined with a back-end component which
handles all of the display system dependent such as specific calls to
X/Windows. This design allows the GNUstep applications to have the
"look and feel" of the underlying display system without any changes to
the application, and the library can be easily ported to other display
systems.
The GNUstep GUI Library requires the GNU Objective-C compiler, the
GNUstep Base Library, the TIFF Graphics library, and a back-end
component like the GNUstep 'Back' Backend.
1.2 Noteworthy changes in version `0.22.0'
==============================
New features include:
* This version is binary incompatible with previous versions due to
the change of NSNotFound in GNUstep base.
* Support for drawing the GUI with a scale factor, for high-DPI
monitors.
* Character panel
* Color picker "Magnifier" tool, for grabbing the color of arbitrary
parts of the screen
Many NSImage improvements (Mac OS X 10.6 drawing methods, better
selection of image reps, better support for icons). Many bugfixes,
including in Xib loading, printing, and NSView geometry.
1.3 Where can you get it? How can you compile it?
==============================
The gstep-gui-0.23.0.tar.gz distribution file has been placed at
`ftp://ftp.gnustep.org/pub/
Read the INSTALL file or the GNUstep-HOWTO for installation
instructions.
1.4 Where do I send bug reports?
==============================
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
==========================
Check out the GNUstep web site. (`http://www.gnustep.org/'), and the
GNU web site. (`http://www.gnu.org/')
GNUstep-make 2.6.3
1 Announcement
**************
The GNUstep Makefile Package version 2.6.3 is now available.
1.1 What is the GNUstep makefile package?
==============================
The makefile package is a simple, powerful and extensible way to write
makefiles for a GNUstep-based project. It allows the user to write a
project without having to deal with the complex issues associated with
configuration, building, installation, and packaging. It also allows
the user to easily create cross-compiled binaries.
1.2 Changes in version `2.6.3'
==============================
Minor bugfix release.
1.3 Obtaining gnustep-make
==========================
You can get the gstep-make-2.6.3.tar.gz distribution file at
`ftp://ftp.gnustep.org/pub/
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
**************
The GNUstep Makefile Package version 2.6.3 is now available.
1.1 What is the GNUstep makefile package?
==============================
The makefile package is a simple, powerful and extensible way to write
makefiles for a GNUstep-based project. It allows the user to write a
project without having to deal with the complex issues associated with
configuration, building, installation, and packaging. It also allows
the user to easily create cross-compiled binaries.
1.2 Changes in version `2.6.3'
==============================
Minor bugfix release.
1.3 Obtaining gnustep-make
==========================
You can get the gstep-make-2.6.3.tar.gz distribution file at
`ftp://ftp.gnustep.org/pub/
Please log bug reports on the GNUstep project page
`http://savannah.gnu.org/bugs/
<bug-gnustep@gnu.org>.
Tuesday, February 12, 2013
Interview with Saul Mora on NSBrief
UPDATE: The interview has been posted. :)
Friday, November 23, 2012
Apportable using GNUstep to port applications from iOS to Android
I have to say I didn't expect this, but it is an awesome thing to see!
Monday, September 03, 2012
Someone Finally Said It...
Someone finally said what I've been thinking all of these years. Though, upon reflection, I think that this comment gives Miguel way too much credit. Something like the GNOME desktop would have started with or without Miguel. The fact of the matter is that there were a lot of objections to Objective-C back then. People weren't used to it's syntax. The climate seems to have changed lately, since Objective-C has passed C++ in popularity according to a recent statistic.
I have watched for a while and observed that GNOME has successfully reinvented the wheel on so many things which OpenStep and Mac OS X already had and, indeed, which GNUstep already had many years before. One amusing recent example was a discussion about using app wrappers in GNOME. Something GNUstep has had since the very beginning.
At any rate, I love GNUstep. It's always been and always will be a labor of love.
I have watched for a while and observed that GNOME has successfully reinvented the wheel on so many things which OpenStep and Mac OS X already had and, indeed, which GNUstep already had many years before. One amusing recent example was a discussion about using app wrappers in GNOME. Something GNUstep has had since the very beginning.
At any rate, I love GNUstep. It's always been and always will be a labor of love.
Monday, February 20, 2012
Official GNUstep presence on GitHub
I'm pleased to announce that we finally have an official presence on GitHub. Currently the mirror updates every few minutes from the SVN repository and is a one way mirror. That will change in the next few days. The repository is here: GNUstep github repository.
I have been working hard to put every single GNUstep repository onto the github account that I've created for this purpose. I should complete this task sometime today or tomorrow so that developers will have access to all of GNUstep's code. Once I'm done with putting all of the code up (there are still 39 more "repositories" to add) I will work on the scripts to make the commits from git propagate to subversion on GNA.
This allows people who are comfortable with git to use it, should they so choose, and allows people who are comfortable with SVN to stay with SVN and gives us a presence on a site which is very popular and has lots of potentially interested developers.
Please let me know if any of you have any questions or comments. :)
Thanks, GC
I have been working hard to put every single GNUstep repository onto the github account that I've created for this purpose. I should complete this task sometime today or tomorrow so that developers will have access to all of GNUstep's code. Once I'm done with putting all of the code up (there are still 39 more "repositories" to add) I will work on the scripts to make the commits from git propagate to subversion on GNA.
This allows people who are comfortable with git to use it, should they so choose, and allows people who are comfortable with SVN to stay with SVN and gives us a presence on a site which is very popular and has lots of potentially interested developers.
Please let me know if any of you have any questions or comments. :)
Thanks, GC
Saturday, July 16, 2011
Banning software patents....
I have been fighting against software patents for years. It's upsetting to see things like this happening:
http://www.widgetpress.com/defense
And this:
http://developers.slashdot.org/story/11/07/16/1152252/UK-Developers-Quit-US-App-Store-Over-Patent-Fears
Doesn't the US realize that we are killing our software industry by doing this? You can't even say that big business believes in software patents anymore since large companies in the US are now also turning against them.
The EU and the UK both rejected software patents for a very good reason. Because they realized that abstract ideas should not be patentable. Software is fundamentally reducible to mathematical algorithms. It is incremental in it's nature and, many times, there is only one way to do things. For all of these reasons and many more.
Most companies today, especially small ones, are forced to patent certain things they do because they need to maintain a patent portfolio. They do this to defend themselves. So, like nuclear weapons, patents proliferate in a sort of MAD (Mutually Assured Destruction) approach.
As an incentive to reform I would like to see the USPTO take a dose of what it is creating. The USPTO should be required to pay a fine for every patent which is found invalid with the money going towards a fund to pay restitution to those who've lost money due to the USPTO's negligence. In addition, it should be an option to sue the USPTO for issuance of a bad patent by either the party holding the patent or the party which was sued due to the issuance of the patent or both.
Ultimately, it is the USPTO putting these weapons of mass destruction in everyone's hands. They should be forced to reap what they've sown.
http://www.widgetpress.com/defense
And this:
http://developers.slashdot.org/story/11/07/16/1152252/UK-Developers-Quit-US-App-Store-Over-Patent-Fears
Doesn't the US realize that we are killing our software industry by doing this? You can't even say that big business believes in software patents anymore since large companies in the US are now also turning against them.
The EU and the UK both rejected software patents for a very good reason. Because they realized that abstract ideas should not be patentable. Software is fundamentally reducible to mathematical algorithms. It is incremental in it's nature and, many times, there is only one way to do things. For all of these reasons and many more.
Most companies today, especially small ones, are forced to patent certain things they do because they need to maintain a patent portfolio. They do this to defend themselves. So, like nuclear weapons, patents proliferate in a sort of MAD (Mutually Assured Destruction) approach.
As an incentive to reform I would like to see the USPTO take a dose of what it is creating. The USPTO should be required to pay a fine for every patent which is found invalid with the money going towards a fund to pay restitution to those who've lost money due to the USPTO's negligence. In addition, it should be an option to sue the USPTO for issuance of a bad patent by either the party holding the patent or the party which was sued due to the issuance of the patent or both.
Ultimately, it is the USPTO putting these weapons of mass destruction in everyone's hands. They should be forced to reap what they've sown.
Saturday, July 02, 2011
Building clang for use with GNUstep
1) Build using the instructions here: http://clang.llvm.org/get_started.html
2) Once that's done, download the latest version of Hans Boehm's garbage collector here: http://www.hpl.hp.com/personal/Hans_Boehm/gc/
3) Untar, Build and install boehm-gc.... it should be gc-7.1.tar.gz
build it with clang like so:
./configure CC=clang LD=gcc && make CC=clang LD=gcc
make install
NOTE: You only need to do step 2 & 3 if you want garbage collection, if not you can skip it.
4) Build gnustep-make like so and install it:
2) Once that's done, download the latest version of Hans Boehm's garbage collector here: http://www.hpl.hp.com/personal/Hans_Boehm/gc/
3) Untar, Build and install boehm-gc.... it should be gc-7.1.tar.gz
build it with clang like so:
./configure CC=clang LD=gcc && make CC=clang LD=gcc
make install
NOTE: You only need to do step 2 & 3 if you want garbage collection, if not you can skip it.
4) Build gnustep-make like so and install it:
./configure CC=clang LD=gcc && make CC=clang LD=gcc
make install
5) Build libobj2 and install it:
make CC=clang CXX=clang++ LD=gcc
make install
6) Build base, gui and back and install them:
./configure CC=clang CXX=clang++ LD=gcc && make CC=clang CXX=clang++ LD=gcc messages=yes
su
. /usr/GNUstep/System/Library/Makefiles/GNUstep.sh && make GNUSTEP_INSTALLATION_DOMAIN=SYSTEM install
That should be all there is too it. Not much, but a few little details which might serve to make it enough of a pain to discourage some people.
Thursday, June 16, 2011
Talk in Western Pennsylvania (Pittsburgh) April 21, 2011 - Report
I realize this is a little late, but I figured that I should post my impressions anyway. First I have to say I was honored when Mark Darymple invited me to come and talk at Cocoaheads in Pittsburgh. I tend to give talks off of the cuff since I don't usually do well sticking to a script and that's what I did at this meeting and it worked fairly well.
The reception of GNUstep was very positive and the members of the group were eager to learn. I got a lot of questions about the project including what we're planning to do with respect to an iOS compatibility layer and also what we're currently working on. I also did get a lot of complaints about how GNUstep looks, in general. I showed them the work that's being done on both Windows and GNOME to improve how GNUstep blends in with those environments using the new theming code. They seemed very impressed by that as well as by Bean.
I did a basic demo of how Gorm works as well as PC and showed them pbxbuild building a Mac OS X project.
Most of the members of the group knew about GNUstep, but didn't know it currently followed Cocoa and some had not followed it in a while since they assumed the project was no longer active. This is one of the many reasons why I am trying to do this talks. To make sure I spread the word that it is still out there and still kicking.
I sincerely thank the people of Cocoaheads, Pittsburgh for giving me the opportunity to come and talk. It was a distinct pleasure meeting each and every one of you. :)
Sunday, January 02, 2011
How to build the GNOME theme...
This article is in response to a request for instructions on how to build the theme...
Given that this is currently very experimental code I didn't think an article about how to use it was in order yet since it's not released, but it makes sense to do this nevertheless. :)
Here's how:
Given that this is currently very experimental code I didn't think an article about how to use it was in order yet since it's not released, but it makes sense to do this nevertheless. :)
Here's how:
- Get the code from SVN per the instructions at the gna.org project page. The URL for the SVN project page is https://gna.org/svn/?group=gnustep
- You should be able to go to the GNUstep project and choose Source Code->Use Subversion and follow the instructions there. Once you check out, the code should be located at gnustep/modules/plugins/themes/GnomeTheme.
- Make certain you have all of the necessary GNOME packages installed as well as their dev equivalents, these include (please let me know if I'm missing anything):
- gtk-x11-2.0
- gdk-x11-2.0
- atk-1.0
- pangoft2.1.0
- gdk_pixbuf-2.0
- pangocairo-1.0
- gio-2.0
- pango-1.0
- gobject-2.0
- gmodule-2.0
- glib-2.0
- gconf-2.0
- Build GNUstep's core libraries... there are plenty of tutorials on how to do this.
- You should then be able to build the GNOME theme and install it simply by doing:
- make
- make install (as root)
- Once that's done, you can start using the theme in one of three ways:
- defaults write NSGlobalDomain GSTheme GnomeTheme
- open the Info panel of the app you want to test the theme with and choose the theme for the application there
- open SystemPreferences and go to the Themes module and choose the theme from the list of themes available there.
Please let me know if there's anything I missed here or if any further information is needed. GC
Wednesday, December 29, 2010
Menu Separator goodness...
Menu separators make a big difference. ;) I know this is a relatively minor change, but it looks excellent with the theme.
Monday, December 27, 2010
More GNOME Theme Improvements
 |
| Bean running with the GNOME native theme |
I considered a few approaches, one was to leverage some of the code I wrote for the Windows theme to generate the menu from the menu structure and create a GtkMenu to attach to the Window... the issue with this approach was that it would have required the window to be a GtkWindow, which wasn't a good idea. The other approach I considered was to reparent the GNUstep created window into a GtkWindow which contains the GtkMenu. The issue with this was that it would have been impossible to switch back to another theme which doesn't use the GNOME widgets and GtkWindow.
The approach I settled on is a good middle ground. The changes fix a number of issues which were present in the code previously. Also, it gives more control to us regarding the look of the in-window menus.
My plans are to work out the remaining bugs with this and release it so that people can start playing with it. I will have more screenshots in the future as it becomes more mature. Feel free to comment on anything you think can be improved. :)
Subscribe to:
Posts (Atom)