Garrett,
I'm also interested in mentoring.
Eric
On Feb 28, 2012 3:17 PM, "Garrett Serack" wrote:
> Thanks Andreas,
>
> ** **
>
> I’m going to push out an update to coapp & devtools today, and then I’m
> going to write up our proposals.
>
> ** **
>
> You mentioned that you could be inte
I know last year there was an interest for CoApp to apply to Google Summer
of Code but it didn't coalesce into an application. Google just announced
that Summer of Code is returning again this year and I would love for us to
become a mentoring organization. CoApp would receive recognition from the
A decision was made also to support self created certificates and provide
some sort of notification to the user that the certificate isn't from a CA.
On Jan 5, 2012 9:16 AM, "Garrett Serack" wrote:
> Not Quite.
>
> Yes, Unsigned packages can not be made. That has always been a line I
> was unwi
So now that I've followed this thread and finally found a chance to
get reply here are my thoughts:
What is required for someone to sign CoApp CLA? I don't remember
offhand, it's been a while.
Certum is probably filled with very nice people but their usability,
especially for non-Polish speakers
In previous message, replace localhost with coapp.org I assume?
On Dec 29, 2011 8:38 PM, "Garrett Serack" wrote:
> Added new pages today:
> Modifying the webstite: http://localhost/developers/modify-website.html
> Transcoding a video using VLC:
> http://localhost/developers/encoding-videos.html
I should be around.
On Dec 29, 2011 8:44 PM, "Garrett Serack" wrote:
> Is anyone going to be around? Can we do a conference call tomorrow?
>
> Hello? Is this thing on? :)
>
> Merry New Year!
>
> G
>
>
>
> ___
> Mailing list: https://launchpad.net/~c
ime, I'll hand code the damn thing up in XAML,
> where I know I can tweak the results until I get where I'm going.
>
> G
> ________
> From: Eric Schultz [wwaha...@gmail.com]
> Sent: Friday, December 23, 2011 11:12 AM
> To: Garrett Serack
&
Is the original Photoshop version of the CoApp logo available on
GitHub? I'm thinking we REALLY need a vector based version of that and
I'm going to see if I can figure something out with that.
Eric
___
Mailing list: https://launchpad.net/~coapp-develop
Hmm, I didn't realize you can get API access to Disqus without paying but
apparently you can. There are some APIs that are restricted to free users.
And quite honestly, even developing a commenting system using the Disqus API
will take more time than just slapping a web browser control in there.
O
While always a huge fan of anything Chrome, Awesomium has licensing that
wouldn't work very well with an open source project. Otherwise, I think it's
a very reasonable plan.
Eric
On Thu, Sep 22, 2011 at 10:31 AM, Garrett Serack wrote:
> Somewhere down the line (1.0, 1.1 maybe) I have the desire
Fredrik,
Just skimming through this and looking at some of the sample files, I see
the use of something along these lines. One issue I see though is that the
standard seems incredibly verbose. Every file in a package must be
checksummed and must have it's own license defined. Also since our packag
Um, the last two give me a 404 error
On Fri, Jul 29, 2011 at 8:15 PM, Garrett Serack wrote:
> http://coapp.org/install -- installs the coapp package manager (not
> really needed explicitly)
>
> http://coapp.org/coapp.devtools.msi -- the current coapp devtools (ptk,
> autopackage, quicktool and
Olaf and Jernej,
I had similar questions when Garrett explained it to me. I was dumbfounded
for at least 15 minutes at the boneheaded-ness of the the Windows Installer
team's decision on this issue. I still have no clue what the heck the people
on the Windows Installer team were thinking. Their de
That seems to be more of a Powershell type thing than a CoApp CLI issue.
Perhaps we can look into making cmdlets at some point.
Eric
On Wed, Jul 20, 2011 at 4:59 AM, Adam Baxter wrote:
> Please implement tab completion!
>
> On Wed, Jul 20, 2011 at 1:33 AM, Garrett Serack
> wrote:
> > I want to
Is there any way this could be done as a table?
Eric
On Tue, Jul 19, 2011 at 1:25 PM, Mark Stone wrote:
> Ok, I've added a comparisons page on our wiki. If Garrett or others
> have additional functional they want to compare or just know about,
> add the item you want to know about on that page a
Hey all,
I just looked at the security advisory and the new Windows APIs for setting
default search directories for DLLs (http://support.microsoft.com/KB/2533623).
I skimmed them looking for a way in which this affects CoApp and nothing
jumps out at me. At the same time, I'm no expert on the Windo
ennis-it@lists.launchpad.net[mailto:
> coapp-developers-bounces+trevor=dennis-it@lists.launchpad.net] *On
> Behalf Of *Eric Schultz
> *Sent:* Thursday, June 09, 2011 8:19 AM
> *To:* Garrett Serack
> *Cc:* coapp-developers
> *Subject:* Re: [Coapp-developers] Ptk exception
>
}
>
>
>
> And tell me what you see… something has got an illegal character in some
> search path
>
>
>
> *From:* coapp-developers-bounces+garretts=microsoft.com@
> lists.launchpad.net [mailto:coapp-developers-bounces+garretts=
> microsoft@lists.launchpa
I've been having this problem with ptk in previous versions and now no
matter what I do. It clearly works for others so I'm not sure what's going
on. Anytime I run ptk, I get an exception which I've attached to this
message. Also, I've attached the input file. (Yes this was to make a fork of
bzip2
Welcome Tim! We're happy to have you on board!
*throws a rock*
On Thu, Jun 2, 2011 at 10:30 AM, Garrett Serack wrote:
> I’d also like to introduce a new member of our team; Tim Rogers.
>
>
>
> Tim is a new full time employee at Microsoft who started this week, and as
> he just found out yesterd
I think it's a cool idea!
As for prizes, Github itself might be someone to talk to. In a lot of cases
this will be using the fork functionality and that's Github's claim to fame,
so to speak. Hell they might even be willing to promote it on their blog.
I think the issue of the type of prizes is d
I had no idea that Github issue tracking was that awesome. DAMN. I love it
here :)
On Thu, Jun 2, 2011 at 11:01 AM, Garrett Serack wrote:
> Wow. Github’s issue tracking is freakin’ awesome.
>
>
>
> Everyone: WATCH THE VIDEO. (Especially *Elizabeth*, who seems to uncover
> bugs by just breathing.
I have a personal preference for a color scheme that is darker like
Fredrik's more. That's my two cents.
On Mon, May 23, 2011 at 11:22 PM, Dj Gilcrease wrote:
> I like Garrets base, but the colors in Fredriks, so I mashed them together
>
___
Mailing lis
*no matter
On Mon, May 23, 2011 at 8:10 PM, Eric Schultz wrote:
> I very much like the font and color Fredrik. I wonder if we could use those
> rich colors somehow not matter what we come up with.
>
>
> On Mon, May 23, 2011 at 7:42 PM, Garrett Serack wrote:
>
>> Hmm.
>
I very much like the font and color Fredrik. I wonder if we could use those
rich colors somehow not matter what we come up with.
On Mon, May 23, 2011 at 7:42 PM, Garrett Serack wrote:
> Hmm.
>
> That's not a bad logo--I'm not sure it's quite right for CoApp either (I'd
> like to avoid actual lett
Laura,
Just want to provide some insight. MSBuild is the executable that can be
used to build VS project file from the command line. I wouldn't be surprised
if VS does that in the background actually. MSDN has some resources on that
I think.
Eric
On Tue, May 17, 2011 at 4:41 PM, wrote:
> On Mo
All,
The input to autopackage currently uses a very basic ini file format. While
very simple, it's a little difficult to describe certain things that way.
Garrett suggested using something along the lines of the format for his
cascading property sheets used in mkSpec. I quickly wrote up a simple
e
Alright we know have a property called COAPP_VERSION with the version number
in it.
On Mon, Apr 18, 2011 at 10:03 AM, Garrett Serack wrote:
> It's not the years, it's the mileage.
>
> :D
>
> ------
> *From:* Eric Schultz [wwaha...@gmail.com
whole new table...
>
> G
> ------
> *From:* Eric Schultz [wwaha...@gmail.com]
> *Sent:* Monday, April 18, 2011 3:06 AM
> *To:* Garrett Serack; coapp-developers
> *Subject:* New CO_VERSION table
>
> All,
>
> I'm adding a CO_VERSION t
All,
I'm adding a CO_VERSION table to packages now. It will always contain one
row with a column of type "string" and category "Version" called
"coapp_version". This, unsurprisingly, will contain the version of CoApp
that created the package. Looking forward, there's may be a point where
there are
out.
Eric
On Thu, Apr 7, 2011 at 8:34 PM, William A. Rowe Jr. wrote:
> On 4/7/2011 8:06 PM, Eric Schultz wrote:
> > I wonder what effect all this will have on CoApp package installation on
> WINE. Obviously
> > that not a pressing issue but its probably something to consider go
his is
man's code!
>
> Given that we have a .NET 4.0 requirement, and Wine doesn't have that...
>
> G
>
> From: Eric Schultz [wwaha...@gmail.com]
> Sent: Thursday, April 07, 2011 6:06 PM
> To: Garrett Serack
> Cc: coapp-developers@
I wonder what effect all this will have on CoApp package installation on
WINE. Obviously that not a pressing issue but its probably something to
consider going forward.
Eric
On Apr 7, 2011 12:27 PM, "Garrett Serack" wrote:
___
Mailing list: https://laun
Of the emergency broadcast system?
On Mon, Mar 21, 2011 at 5:43 PM, Garrett Serack wrote:
> I don't seem to be getting messages anymore.
>
> This is a test.
>
> G
>
> ___
> Mailing list: https://launchpad.net/~coapp-developers
> Post to : coapp-d
A bit involved? It is a beautiful process that simply could never be
improved upon :)
Alright maybe it could be A LITTLE :)
On Feb 3, 2011 10:15 AM, "Garrett Serack" wrote:
> Howdy folks,
>
> I'll be publishing our first binaries next week (command line package
installer, trace, scan mkPackage to
Translation: Garrett will be responding to messages on the list by Monday
night :)
On Fri, Nov 19, 2010 at 2:46 PM, Garrett Serack wrote:
> Just an FYI, I’ve pushed a lot of changes to a lot of the managed
> projects (toolkit, etc)
>
>
>
> If you have been playing around with the source pull upd
I have a tiny bit when I automated signing a library when it was built but
you probably have just as much as me.
Eric
On Mon, Nov 15, 2010 at 11:07 AM, Garrett Serack wrote:
> I’m starting on the mkProject tool now (VERY EXCITING!!) :D
>
>
>
> I’m wondering if anyone on the list has (extensive/
Lee,
I think that one of the main reasons open source software often uses static
libraries, especially on Windows, is that it gets around a lot of the
dependency issues. You don't have to worry about dynamically loading a
strange version of a dependency library if you never dynamically load
librar
John,
I'm heading up mkPackage which creates the actual MSI files for CoApp
packages. I will be the first person to tell you MSI is a pain to deal with
and I can say much of it from first hand experience dealing with it. I
wouldn't want anyone to have to make MSI packages by hand which is the
reas
But Rafael, does it use WinSxS? :)
On Sep 11, 2010 12:28 AM, "Rivera, Rafael" wrote:
> Yep, agreed. My Hello World app can print that xml out too.
>
> /rafael
>
> On 9/11/2010 12:33 AM, Nasser Dassi wrote:
>> Ahem. That's not proof that you're NOT crazy. That's just proof that
>> WinSxS binding p
Is there a command for pulling all the project updates at once?
On Tue, Aug 31, 2010 at 9:29 PM, Jobin Augustine wrote:
> Hi Garrett,
>
> I think we can keep this information in wiki or something like that.
> because users like me require frequent reference for setup.
> do we already have a pl
Is there a command for pulling all the project updates at once?
On Tue, Aug 31, 2010 at 9:29 PM, Jobin Augustine wrote:
> Hi Garrett,
>
> I think we can keep this information in wiki or something like that.
> because users like me require frequent reference for setup.
> do we already have a pl
The question I asked about modifying the registry and path information made
me think some more about what type of system modifications CoApp packages
should be allowed to do. Here are a few I can think of (they pretty much
come from the Wix schemas and the relevant elements are in included in
paren
Actually, I'm working on mkPackage, not mkProject :)
On Sep 1, 2010 4:26 PM, "William A. Rowe Jr." wrote:
> On 9/1/2010 12:19 PM, Elizabeth M Smith wrote:
>>
>> Why not just use the native windows API file functions instead of the C
runtime versions -
>> this is definitely a windows only product
Gang,
I've got mkPackage working reasonably well for non-application packages. I'm
starting to think about what type of modifications each type of package
should be able to perform to the system whether it be adding something to
the system PATH variable or creating a variable (like Wix does), regi
Gang,
http://coapp.org/Blueprints/Package_Blueprint/Additional_Notes describes two
different install locations for packages.
First, one example is: c:\apps\.installed\coapp\zlib\1.2.3 which seems to
correspond to: {$VENDOR}\{$PRODUCTNAME}\{$VERSION}
However further down the page I see:
{$INSTALL
Hi everyone, hope your weekend is starting well. I've got a few questions
for the group.
- With a SharedLib will there ever be a file with that role that is NOT part
of an assembly? For example, let's say we are installing a package to
c:\apps\.installed\coapp\python\2.6.1.1. In this folder, we ha
I know that Garrett. :) I just read it wrong.
Please everyone, I know that ia64 and x64 are different :)
On Aug 20, 2010 8:49 AM, "Garrett Serack" wrote:
> ROFL.
>
> IA64 != x64.
>
> However x64 == AMD64 == EMT64 == x86-x64.
>
> g
>
> From: Eric Schul
I misunderstood Garrett reply, I thought he meant x64 packages weren't going
to work in general.
On Fri, Aug 20, 2010 at 8:28 AM, Olaf van der Spek wrote:
> On Fri, Aug 20, 2010 at 3:26 PM, Eric Schultz wrote:
> > Wait now, what's going on with x64?
>
&
Wait now, what's going on with x64?
On Fri, Aug 20, 2010 at 8:05 AM, Garrett Serack wrote:
> X86 packages *should* run ok.
>
> X64 packages won't ... IA64 is dead anyway.
>
> g
>
> -Original Message-
> From:
> coapp-developers-bounces+garretts=microsoft@lists.launchpad.net[mailto:
>
I just wanted to make sure, we're not intending to provide support for IA 64
(Itanium) are we?
Eric
___
Mailing list: https://launchpad.net/~coapp-developers
Post to : coapp-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~coapp-de
This is mainly a question for Garrett but I figured someone else might
stumble upon this issue too so I figured I'd send it to all.
I'm creating an XSD schema to describe the input xml for mkPackage. For that
I want to be able to restrict the type of data entered into certain
attributes. These are
me version
numbers?
I think this is why no one uses SxS assemblies, man they're confusing! :)
On Thu, Aug 12, 2010 at 8:48 PM, Garrett Serack wrote:
> Yeah... components in MSI are more fine grained than you think. An install
> is almost always made up of many components.
>
>
2, 2010 at 6:50 PM, Rivera, Rafael
> wrote:
>
> Oh, sorry. Wow. I just fell into that GUID-being-a-real-GUID trap that was
> just talked about moments ago. Yikes.
>
> /rafael
>
>
>
> On 8/12/2010 8:49 PM, Eric Schultz wrote:
>
> Rafael,
>
>
>
> We w
My thoughts on ProductCode are just create another 'HUID' but append the
word "product" to the name, version, architecture and public key token
before hashing. That way every time they build the same package, the
ProductCode is also the same.
Not really sure how to do for the Guid attribute for ea
keeping our required data separate, it makes it easier to
> one day abandon MSI (if things came to that). On the other hand, if it’s not
> too hard, why not merge them. I’ll let you make the call.
>
>
>
> Although, platform, don’t trust the MSI version of that… it’s evil.
>
>
Rafael,
We want to be able to provide a consistent ID for a package no matter how
many times its built. By using the package name, version, architecture and
the publisher's public key token, the same package will always have the same
ID.
Eric
On Thu, Aug 12, 2010 at 7:43 PM, Rivera, Rafael wrote
>
> I don't think we should call this a GUID if you're not using the official
> definition of a GUID/UUID from RFC 4122. If I see GUID in documentation,
> I'm going to assume I can call a normal GUID creation function to create
> one.
I think you bring up a good point Trevor. I'm a bit of a stic
Hey gang,
One quick question regarding the MSI tables, one little more complex one
and some food for thought.
- On CO_TAGS, I understand that it holds keywords so what is the type column
there for? Are there different types of keywords?
- Regarding CO_BINDING_POLICY, as Garrett said this is nee
Ah. Well I know WiX compresses .NET custom actions with any referenced
assemblies needed by the action. There's some custom action that they use to
handle that I'm sure.
Eric
On Wed, Aug 11, 2010 at 3:15 PM, Olaf van der Spek wrote:
> On Wed, Aug 11, 2010 at 10:15 PM, Eric S
In my experience with simple MSIs that I've zipped, you don't gain very much
since the actual files are already compressed. I think custom actions are
uncompressed so to the best of my knowledge that'd be the largest
non-compressed portion of the MSI. In our case though, we have a single
custom act
Garrett and gang,
I've been meaning to actually get involved in developing CoApp over the
summer so now I'm actually going to do it! Are there any particular
areas/sub-projects that need addressing? Basically I'm asking, what do you
need someone to code?
Eric
_
Andrew,
I'm on Gmail too and had a similar problem. The way around it is to use
Reply All instead of Reply. Your message should go to the mailing list.
Eric
On Jul 26, 2010 11:07 PM, "Andrew Fenn" wrote:
> Is there anyway to get the mailing list to show the from address as the
list
> rather the
I haven't seen this come up in the mailing lists or the wiki but I'm
wondering what thought has been put into the usage scenario where a package
requires software non-CoApp. The main example in my mind would be a package
that requires the newest version of the .NET Framework but the user doesn't
cu
64 matches
Mail list logo
