Menu
▾
▴
subtext-devs — For devs of Subtext. Please keep non-dev discussion in the subtext-users list.
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(238) |
Jun
(130) |
Jul
(92) |
Aug
(54) |
Sep
(12) |
Oct
(30) |
Nov
(26) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(126) |
Feb
(592) |
Mar
(301) |
Apr
(266) |
May
(147) |
Jun
(220) |
Jul
(261) |
Aug
(704) |
Sep
(227) |
Oct
(239) |
Nov
(561) |
Dec
(273) |
| 2007 |
Jan
(331) |
Feb
(443) |
Mar
(294) |
Apr
(512) |
May
(316) |
Jun
(213) |
Jul
(66) |
Aug
(135) |
Sep
(189) |
Oct
(150) |
Nov
(77) |
Dec
(39) |
| 2008 |
Jan
(26) |
Feb
(28) |
Mar
(112) |
Apr
(197) |
May
(121) |
Jun
(131) |
Jul
(251) |
Aug
(388) |
Sep
(79) |
Oct
(54) |
Nov
(69) |
Dec
(133) |
| 2009 |
Jan
(114) |
Feb
(7) |
Mar
(86) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
|
From: Phil H. <ph...@mi...> - 2009-03-28 05:04:05
|
Hi All, I'd like to remove the .TEXT import code (but keep the SQL script). The following issue contains the justification. http://code.google.com/p/subtext/issues/detail?id=11 Long story short, the code has much less value now than it did back then and less code == easier maintenance. Another piece of code I'm struggling with is our WATIN tests. I'm thinking we may want to remove them because they're out of date and nobody seems to have the time to maintain them. Phil |
|
From: Christopher <chr...@bl...> - 2009-03-28 03:39:29
|
1. you need sqldmo installed to build - I was able to find a copy on the netterwebs, but it wasn't easy. Is it wise to include a dependency on sql2000 technology? 2. after registering sqldmo, the unittests project is complaining about Microsoft.SqlServer.Management.Smo namespace, actually it looks like it can't see Microsoft.SqlServer.Anything - the DatabaseHelper class is pretty hosed (42 errors) this is on Vista, clean checkout from the new repo. -- -Christopher | http://bluefenix.net 2009/3/27 Phil Haack <ph...@mi...>: > Hi All, > > > > We are live on Google Code! http://code.google.com/p/subtext/ > > > > One cool thing about Google Code is how well it associates checkins with > issues if you follow the guidelines: > http://code.google.com/p/subtext/wiki/DeveloperGuide > > > > For now, let’s continue to use this mailing list for developer discussions. > For forums, let’s use http://groups.google.com/group/subtext > > > > For issues, we’ll use http://code.google.com/p/subtext/issues/list > > > > As we’re ready to fix items, we can copy associated issues from SourceForge > manually. I’ve copied a few already which are all assigned to me. If you > want to work on any of them, assign them to yourself. > > > > If you don’t have commit access yet, just attach a patch to an issue and one > of us will merge it in and/or grant you commit access. I’d like to have > tighter review process around code commits and accepting committers. One > cool thing about Google Code is you can request code reviews for commits > etc… via a commit checkin comment. > > > > http://code.google.com/p/support/wiki/CodeReviews > > > > Phil > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Christopher <chr...@bl...> - 2009-03-28 03:25:28
|
if I remove unittests and watintests, it builds just fine. -- -Christopher | http://bluefenix.net On Fri, Mar 27, 2009 at 10:13 PM, Christopher <chr...@bl...> wrote: > 1. you need sqldmo installed to build - I was able to find a copy on > the netterwebs, but it wasn't easy. Is it wise to include a dependency > on sql2000 technology? > > 2. after registering sqldmo, the unittests project is complaining > about Microsoft.SqlServer.Management.Smo namespace, actually it looks > like it can't see Microsoft.SqlServer.Anything - the DatabaseHelper > class is pretty hosed (42 errors) > > this is on Vista, clean checkout from the new repo. > -- > -Christopher | http://bluefenix.net > > > > 2009/3/27 Phil Haack <ph...@mi...>: >> Hi All, >> >> >> >> We are live on Google Code! http://code.google.com/p/subtext/ >> >> >> >> One cool thing about Google Code is how well it associates checkins with >> issues if you follow the guidelines: >> http://code.google.com/p/subtext/wiki/DeveloperGuide >> >> >> >> For now, let’s continue to use this mailing list for developer discussions. >> For forums, let’s use http://groups.google.com/group/subtext >> >> >> >> For issues, we’ll use http://code.google.com/p/subtext/issues/list >> >> >> >> As we’re ready to fix items, we can copy associated issues from SourceForge >> manually. I’ve copied a few already which are all assigned to me. If you >> want to work on any of them, assign them to yourself. >> >> >> >> If you don’t have commit access yet, just attach a patch to an issue and one >> of us will merge it in and/or grant you commit access. I’d like to have >> tighter review process around code commits and accepting committers. One >> cool thing about Google Code is you can request code reviews for commits >> etc… via a commit checkin comment. >> >> >> >> http://code.google.com/p/support/wiki/CodeReviews >> >> >> >> Phil >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > |
|
From: Phil H. <ph...@mi...> - 2009-03-28 01:50:55
|
p.s. I'll still use subtext-commits on sourceforge for commit emails. Feels weird to create a whole nother Google group just for commit emails and I don't want to spam the main group with commit emails. Any thoughts? Phil From: Jon Galloway [mailto:jon...@gm...] Sent: Friday, March 27, 2009 4:53 PM To: sub...@li... Subject: Re: [Subtext-devs] We are now live on Google Code! Sounds good. Why stay on sourceforge for mailing lists? Any advantage over moving to Google discussions? I mean, if you're gonna move, might as well do it all at once. 2009/3/27 Steven Harman <ste...@gm...<mailto:ste...@gm...>> Branch-per-feature is precisely the way I'd like to work... assuming the SCM supported branch/fork & merge as first-class citizens. An SCM like, say... Git does just that. :) I'm fine with doing it in SVN as well, it just sucks that all of the branching has to happen remotely, on the centralized repository, as that causes a good deal of noise. Anyhow... let's try it, and if it falls on its face, we'll try something else. -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...<mailto:ph...@mi...>> After reading through http://code.google.com/p/support/wiki/CodeReviews more carefully, it sounds like their recommended approach is that developers do their work on a major feature in a private branch. Then when the feature work is done, they request a code review before merging it into trunk. Kind of a neat idea. What do you guys think about using that as our new workflow? If we did that, I'd be happy to be a bit more liberal with giving commit access out. Tiny changes could still happen in trunk. But med to large features should be done in a private branch. Phil From: Phil Haack [mailto:ph...@mi...<mailto:ph...@mi...>] Sent: Friday, March 27, 2009 4:25 PM To: sub...@li...<mailto:sub...@li...> Subject: [Subtext-devs] We are now live on Google Code! Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let's continue to use this mailing list for developer discussions. For forums, let's use http://groups.google.com/group/subtext For issues, we'll use http://code.google.com/p/subtext/issues/list As we're ready to fix items, we can copy associated issues from SourceForge manually. I've copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don't have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I'd like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc... via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs |
|
From: Phil H. <ph...@mi...> - 2009-03-28 01:50:00
|
I guess we can make the switch right now if everyone is ready. Please join the Subtext Google Group now and we can retire the SourceForge mailing list. Perhaps the one feature I still like with SourceForge. ;) http://groups.google.com/group/subtext From: Jon Galloway [mailto:jon...@gm...] Sent: Friday, March 27, 2009 4:53 PM To: sub...@li... Subject: Re: [Subtext-devs] We are now live on Google Code! Sounds good. Why stay on sourceforge for mailing lists? Any advantage over moving to Google discussions? I mean, if you're gonna move, might as well do it all at once. 2009/3/27 Steven Harman <ste...@gm...<mailto:ste...@gm...>> Branch-per-feature is precisely the way I'd like to work... assuming the SCM supported branch/fork & merge as first-class citizens. An SCM like, say... Git does just that. :) I'm fine with doing it in SVN as well, it just sucks that all of the branching has to happen remotely, on the centralized repository, as that causes a good deal of noise. Anyhow... let's try it, and if it falls on its face, we'll try something else. -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...<mailto:ph...@mi...>> After reading through http://code.google.com/p/support/wiki/CodeReviews more carefully, it sounds like their recommended approach is that developers do their work on a major feature in a private branch. Then when the feature work is done, they request a code review before merging it into trunk. Kind of a neat idea. What do you guys think about using that as our new workflow? If we did that, I'd be happy to be a bit more liberal with giving commit access out. Tiny changes could still happen in trunk. But med to large features should be done in a private branch. Phil From: Phil Haack [mailto:ph...@mi...<mailto:ph...@mi...>] Sent: Friday, March 27, 2009 4:25 PM To: sub...@li...<mailto:sub...@li...> Subject: [Subtext-devs] We are now live on Google Code! Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let's continue to use this mailing list for developer discussions. For forums, let's use http://groups.google.com/group/subtext For issues, we'll use http://code.google.com/p/subtext/issues/list As we're ready to fix items, we can copy associated issues from SourceForge manually. I've copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don't have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I'd like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc... via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs |
|
From: Phil H. <ph...@mi...> - 2009-03-28 01:49:07
|
I agree, the branching is not as nice as it would be with GIT, but I think the code review feature will hopefully make up for it. If it falls flat, as you say, we can always re-evaluate GIT. I’ve just found the tools to be lacking on Windows and I’ve really got the hang of SVN. ;) It’s getting harder to teach this old dog new tricks. It would be interesting to see if Google Code will ever support GIT. Phil From: Steven Harman [mailto:ste...@gm...] Sent: Friday, March 27, 2009 4:49 PM To: sub...@li... Subject: Re: [Subtext-devs] We are now live on Google Code! Branch-per-feature is precisely the way I'd like to work... assuming the SCM supported branch/fork & merge as first-class citizens. An SCM like, say... Git does just that. :) I'm fine with doing it in SVN as well, it just sucks that all of the branching has to happen remotely, on the centralized repository, as that causes a good deal of noise. Anyhow... let's try it, and if it falls on its face, we'll try something else. -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...<mailto:ph...@mi...>> After reading through http://code.google.com/p/support/wiki/CodeReviews more carefully, it sounds like their recommended approach is that developers do their work on a major feature in a private branch. Then when the feature work is done, they request a code review before merging it into trunk. Kind of a neat idea. What do you guys think about using that as our new workflow? If we did that, I’d be happy to be a bit more liberal with giving commit access out. Tiny changes could still happen in trunk. But med to large features should be done in a private branch. Phil From: Phil Haack [mailto:ph...@mi...<mailto:ph...@mi...>] Sent: Friday, March 27, 2009 4:25 PM To: sub...@li...<mailto:sub...@li...> Subject: [Subtext-devs] We are now live on Google Code! Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let’s continue to use this mailing list for developer discussions. For forums, let’s use http://groups.google.com/group/subtext For issues, we’ll use http://code.google.com/p/subtext/issues/list As we’re ready to fix items, we can copy associated issues from SourceForge manually. I’ve copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don’t have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I’d like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc… via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs |
|
From: Jon G. <jon...@gm...> - 2009-03-27 23:53:15
|
Sounds good. Why stay on sourceforge for mailing lists? Any advantage over moving to Google discussions? I mean, if you're gonna move, might as well do it all at once. 2009/3/27 Steven Harman <ste...@gm...> > Branch-per-feature is precisely the way I'd like to work... assuming the > SCM supported branch/fork & merge as first-class citizens. An SCM like, > say... Git does just that. :) > > I'm fine with doing it in SVN as well, it just sucks that all of the > branching has to happen remotely, on the centralized repository, as that > causes a good deal of noise. Anyhow... let's try it, and if it falls on its > face, we'll try something else. > > -steve > > //---- 90% of being smart is knowing what you're dumb at ----// > http://stevenharman.net/ > > > 2009/3/27 Phil Haack <ph...@mi...> > >> After reading through http://code.google.com/p/support/wiki/CodeReviewsmore carefully, it sounds like their recommended approach is that developers >> do their work on a major feature in a private branch. Then when the feature >> work is done, they request a code review before merging it into trunk. Kind >> of a neat idea. >> >> >> >> What do you guys think about using that as our new workflow? If we did >> that, I’d be happy to be a bit more liberal with giving commit access out. >> >> >> >> Tiny changes could still happen in trunk. But med to large features should >> be done in a private branch. >> >> >> >> Phil >> >> >> >> *From:* Phil Haack [mailto:ph...@mi...] >> *Sent:* Friday, March 27, 2009 4:25 PM >> *To:* sub...@li... >> *Subject:* [Subtext-devs] We are now live on Google Code! >> >> >> >> Hi All, >> >> >> >> We are live on Google Code! http://code.google.com/p/subtext/ >> >> >> >> One cool thing about Google Code is how well it associates checkins with >> issues if you follow the guidelines: >> http://code.google.com/p/subtext/wiki/DeveloperGuide >> >> >> >> For now, let’s continue to use this mailing list for developer >> discussions. For forums, let’s use http://groups.google.com/group/subtext >> >> >> >> For issues, we’ll use http://code.google.com/p/subtext/issues/list >> >> >> >> As we’re ready to fix items, we can copy associated issues from >> SourceForge manually. I’ve copied a few already which are all assigned to >> me. If you want to work on any of them, assign them to yourself. >> >> >> >> If you don’t have commit access yet, just attach a patch to an issue and >> one of us will merge it in and/or grant you commit access. I’d like to have >> tighter review process around code commits and accepting committers. One >> cool thing about Google Code is you can request code reviews for commits >> etc… via a commit checkin comment. >> >> >> >> http://code.google.com/p/support/wiki/CodeReviews >> >> >> >> Phil >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Steven H. <ste...@gm...> - 2009-03-27 23:49:01
|
Branch-per-feature is precisely the way I'd like to work... assuming the SCM supported branch/fork & merge as first-class citizens. An SCM like, say... Git does just that. :) I'm fine with doing it in SVN as well, it just sucks that all of the branching has to happen remotely, on the centralized repository, as that causes a good deal of noise. Anyhow... let's try it, and if it falls on its face, we'll try something else. -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...> > After reading through http://code.google.com/p/support/wiki/CodeReviewsmore carefully, it sounds like their recommended approach is that developers > do their work on a major feature in a private branch. Then when the feature > work is done, they request a code review before merging it into trunk. Kind > of a neat idea. > > > > What do you guys think about using that as our new workflow? If we did > that, I’d be happy to be a bit more liberal with giving commit access out. > > > > Tiny changes could still happen in trunk. But med to large features should > be done in a private branch. > > > > Phil > > > > *From:* Phil Haack [mailto:ph...@mi...] > *Sent:* Friday, March 27, 2009 4:25 PM > *To:* sub...@li... > *Subject:* [Subtext-devs] We are now live on Google Code! > > > > Hi All, > > > > We are live on Google Code! http://code.google.com/p/subtext/ > > > > One cool thing about Google Code is how well it associates checkins with > issues if you follow the guidelines: > http://code.google.com/p/subtext/wiki/DeveloperGuide > > > > For now, let’s continue to use this mailing list for developer discussions. > For forums, let’s use http://groups.google.com/group/subtext > > > > For issues, we’ll use http://code.google.com/p/subtext/issues/list > > > > As we’re ready to fix items, we can copy associated issues from SourceForge > manually. I’ve copied a few already which are all assigned to me. If you > want to work on any of them, assign them to yourself. > > > > If you don’t have commit access yet, just attach a patch to an issue and > one of us will merge it in and/or grant you commit access. I’d like to have > tighter review process around code commits and accepting committers. One > cool thing about Google Code is you can request code reviews for commits > etc… via a commit checkin comment. > > > > http://code.google.com/p/support/wiki/CodeReviews > > > > Phil > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Travis I. <ti...@pa...> - 2009-03-27 23:35:39
|
I'm a big fan of the task branch mechanism. We use that at work and it's really helpful when you have a bunch of people working on different things at the same time. Helps to track what changes went into which feature, too. Add code reviews and I think it's a big win. -T -- Travis Illig http://www.paraesthesia.com 2009/3/27 Phil Haack <ph...@mi...> > After reading through http://code.google.com/p/support/wiki/CodeReviewsmore carefully, it sounds like their recommended approach is that developers > do their work on a major feature in a private branch. Then when the feature > work is done, they request a code review before merging it into trunk. Kind > of a neat idea. > > > > What do you guys think about using that as our new workflow? If we did > that, I’d be happy to be a bit more liberal with giving commit access out. > > > > Tiny changes could still happen in trunk. But med to large features should > be done in a private branch. > > > > Phil > > > > *From:* Phil Haack [mailto:ph...@mi...] > *Sent:* Friday, March 27, 2009 4:25 PM > *To:* sub...@li... > *Subject:* [Subtext-devs] We are now live on Google Code! > > > > Hi All, > > > > We are live on Google Code! http://code.google.com/p/subtext/ > > > > One cool thing about Google Code is how well it associates checkins with > issues if you follow the guidelines: > http://code.google.com/p/subtext/wiki/DeveloperGuide > > > > For now, let’s continue to use this mailing list for developer discussions. > For forums, let’s use http://groups.google.com/group/subtext > > > > For issues, we’ll use http://code.google.com/p/subtext/issues/list > > > > As we’re ready to fix items, we can copy associated issues from SourceForge > manually. I’ve copied a few already which are all assigned to me. If you > want to work on any of them, assign them to yourself. > > > > If you don’t have commit access yet, just attach a patch to an issue and > one of us will merge it in and/or grant you commit access. I’d like to have > tighter review process around code commits and accepting committers. One > cool thing about Google Code is you can request code reviews for commits > etc… via a commit checkin comment. > > > > http://code.google.com/p/support/wiki/CodeReviews > > > > Phil > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Phil H. <ph...@mi...> - 2009-03-27 23:31:18
|
After reading through http://code.google.com/p/support/wiki/CodeReviews more carefully, it sounds like their recommended approach is that developers do their work on a major feature in a private branch. Then when the feature work is done, they request a code review before merging it into trunk. Kind of a neat idea. What do you guys think about using that as our new workflow? If we did that, I'd be happy to be a bit more liberal with giving commit access out. Tiny changes could still happen in trunk. But med to large features should be done in a private branch. Phil From: Phil Haack [mailto:ph...@mi...] Sent: Friday, March 27, 2009 4:25 PM To: sub...@li... Subject: [Subtext-devs] We are now live on Google Code! Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let's continue to use this mailing list for developer discussions. For forums, let's use http://groups.google.com/group/subtext For issues, we'll use http://code.google.com/p/subtext/issues/list As we're ready to fix items, we can copy associated issues from SourceForge manually. I've copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don't have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I'd like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc... via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil |
|
From: Phil H. <ph...@mi...> - 2009-03-27 23:25:41
|
Hi All, We are live on Google Code! http://code.google.com/p/subtext/ One cool thing about Google Code is how well it associates checkins with issues if you follow the guidelines: http://code.google.com/p/subtext/wiki/DeveloperGuide For now, let's continue to use this mailing list for developer discussions. For forums, let's use http://groups.google.com/group/subtext For issues, we'll use http://code.google.com/p/subtext/issues/list As we're ready to fix items, we can copy associated issues from SourceForge manually. I've copied a few already which are all assigned to me. If you want to work on any of them, assign them to yourself. If you don't have commit access yet, just attach a patch to an issue and one of us will merge it in and/or grant you commit access. I'd like to have tighter review process around code commits and accepting committers. One cool thing about Google Code is you can request code reviews for commits etc... via a commit checkin comment. http://code.google.com/p/support/wiki/CodeReviews Phil |
|
From: Phil H. <ph...@mi...> - 2009-03-27 22:06:10
|
I made it read-only for now. It’s possible to completely disable subversion, which we can do later. I added a readme for now. Phil From: Steven Harman [mailto:ste...@gm...] Sent: Friday, March 27, 2009 10:48 AM To: sub...@li... Subject: Re: [Subtext-devs] No Checkins! perhaps it would be good to change the SF repo to be read-only - or maybe just archive the existing trunk into a branch, and then replace the current TRUNK with a README file explaining the code has moved to a new home? -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...<mailto:ph...@mi...>> No way to import bugs. I’m just going to add new bugs to Google Code as I’m ready to fix them. Let’s try to make sure to add a bug for fix we do except for simple refactorings where no functionality changes. Simo, you have access now. The import is complete! Phil From: Simone Chiaretta [mailto:sim...@gm...<mailto:sim...@gm...>] Sent: Thursday, March 26, 2009 1:45 AM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] No Checkins! Btw... just looked on google code... seems like now everything (at least the source code) is online. Is there a way to import old tasks and bugs from SF as well? Simo On Thu, Mar 26, 2009 at 9:41 AM, Simone Chiaretta <sim...@gm...<mailto:sim...@gm...>> wrote: Wow... that is a very long import.. 2009/3/25 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Still ongoing. It's a slow operation. Once it's in there, I'll give access. ________________________________ From: Simone Chiaretta [sim...@gm...<mailto:sim...@gm...>] Sent: Monday, March 23, 2009 10:43 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] No Checkins! Great... let us know when the change is done. Furthermore, can you add me to the project's admins as well? Thx Simo 2009/3/24 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Hi All, I’m going to be moving Subtext’s svn repro to Google Code. Please, no checkins for the time being or they will not be transferred. Phil ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs |
|
From: Simone C. <sim...@gm...> - 2009-03-27 17:55:21
|
And also change the description of the project saying that it was moved. And maybe also a post somewhere :) Simo 2009/3/27 Steven Harman <ste...@gm...> > perhaps it would be good to change the SF repo to be read-only - or maybe > just archive the existing trunk into a branch, and then replace the current > TRUNK with a README file explaining the code has moved to a new home? > > -steve > > //---- 90% of being smart is knowing what you're dumb at ----// > http://stevenharman.net/ > > > 2009/3/27 Phil Haack <ph...@mi...> > >> No way to import bugs. I’m just going to add new bugs to Google Code as >> I’m ready to fix them. Let’s try to make sure to add a bug for fix we do >> except for simple refactorings where no functionality changes. >> >> >> >> Simo, you have access now. The import is complete! >> >> >> >> Phil >> >> >> >> *From:* Simone Chiaretta [mailto:sim...@gm...] >> *Sent:* Thursday, March 26, 2009 1:45 AM >> >> *To:* sub...@li... >> *Subject:* Re: [Subtext-devs] No Checkins! >> >> >> >> Btw... just looked on google code... seems like now everything (at least >> the source code) is online. >> Is there a way to import old tasks and bugs from SF as well? >> Simo >> >> On Thu, Mar 26, 2009 at 9:41 AM, Simone Chiaretta < >> sim...@gm...> wrote: >> >> Wow... that is a very long import.. >> >> 2009/3/25 Phil Haack <ph...@mi...> >> >> Still ongoing. It's a slow operation. Once it's in there, I'll give >> access. >> ------------------------------ >> >> *From:* Simone Chiaretta [sim...@gm...] >> *Sent:* Monday, March 23, 2009 10:43 PM >> *To:* sub...@li... >> *Subject:* Re: [Subtext-devs] No Checkins! >> >> Great... let us know when the change is done. >> Furthermore, can you add me to the project's admins as well? >> Thx >> Simo >> >> 2009/3/24 Phil Haack <ph...@mi...> >> >> Hi All, >> >> >> >> I’m going to be moving Subtext’s svn repro to Google Code. Please, no >> checkins for the time being or they will not be transferred. >> >> >> >> Phil >> >> >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> >> >> >> -- >> Simone Chiaretta >> codeclimber.net.nz >> Any sufficiently advanced technology is indistinguishable from magic >> "Life is short, play hard" >> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> >> >> >> -- >> Simone Chiaretta >> codeclimber.net.nz >> Any sufficiently advanced technology is indistinguishable from magic >> "Life is short, play hard" >> >> >> >> >> -- >> Simone Chiaretta >> codeclimber.net.nz >> Any sufficiently advanced technology is indistinguishable from magic >> "Life is short, play hard" >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta codeclimber.net.nz Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Steven H. <ste...@gm...> - 2009-03-27 17:48:32
|
perhaps it would be good to change the SF repo to be read-only - or maybe just archive the existing trunk into a branch, and then replace the current TRUNK with a README file explaining the code has moved to a new home? -steve //---- 90% of being smart is knowing what you're dumb at ----// http://stevenharman.net/ 2009/3/27 Phil Haack <ph...@mi...> > No way to import bugs. I’m just going to add new bugs to Google Code as > I’m ready to fix them. Let’s try to make sure to add a bug for fix we do > except for simple refactorings where no functionality changes. > > > > Simo, you have access now. The import is complete! > > > > Phil > > > > *From:* Simone Chiaretta [mailto:sim...@gm...] > *Sent:* Thursday, March 26, 2009 1:45 AM > > *To:* sub...@li... > *Subject:* Re: [Subtext-devs] No Checkins! > > > > Btw... just looked on google code... seems like now everything (at least > the source code) is online. > Is there a way to import old tasks and bugs from SF as well? > Simo > > On Thu, Mar 26, 2009 at 9:41 AM, Simone Chiaretta < > sim...@gm...> wrote: > > Wow... that is a very long import.. > > 2009/3/25 Phil Haack <ph...@mi...> > > Still ongoing. It's a slow operation. Once it's in there, I'll give access. > ------------------------------ > > *From:* Simone Chiaretta [sim...@gm...] > *Sent:* Monday, March 23, 2009 10:43 PM > *To:* sub...@li... > *Subject:* Re: [Subtext-devs] No Checkins! > > Great... let us know when the change is done. > Furthermore, can you add me to the project's admins as well? > Thx > Simo > > 2009/3/24 Phil Haack <ph...@mi...> > > Hi All, > > > > I’m going to be moving Subtext’s svn repro to Google Code. Please, no > checkins for the time being or they will not be transferred. > > > > Phil > > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > -- > Simone Chiaretta > codeclimber.net.nz > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > > > > -- > Simone Chiaretta > codeclimber.net.nz > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > > > > > -- > Simone Chiaretta > codeclimber.net.nz > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > |
|
From: Phil H. <ph...@mi...> - 2009-03-27 17:16:56
|
No way to import bugs. I'm just going to add new bugs to Google Code as I'm ready to fix them. Let's try to make sure to add a bug for fix we do except for simple refactorings where no functionality changes. Simo, you have access now. The import is complete! Phil From: Simone Chiaretta [mailto:sim...@gm...] Sent: Thursday, March 26, 2009 1:45 AM To: sub...@li... Subject: Re: [Subtext-devs] No Checkins! Btw... just looked on google code... seems like now everything (at least the source code) is online. Is there a way to import old tasks and bugs from SF as well? Simo On Thu, Mar 26, 2009 at 9:41 AM, Simone Chiaretta <sim...@gm...<mailto:sim...@gm...>> wrote: Wow... that is a very long import.. 2009/3/25 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Still ongoing. It's a slow operation. Once it's in there, I'll give access. ________________________________ From: Simone Chiaretta [sim...@gm...<mailto:sim...@gm...>] Sent: Monday, March 23, 2009 10:43 PM To: sub...@li...<mailto:sub...@li...> Subject: Re: [Subtext-devs] No Checkins! Great... let us know when the change is done. Furthermore, can you add me to the project's admins as well? Thx Simo 2009/3/24 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Hi All, I'm going to be moving Subtext's svn repro to Google Code. Please, no checkins for the time being or they will not be transferred. Phil ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" ------------------------------------------------------------------------------ _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Simone C. <sim...@gm...> - 2009-03-26 08:44:45
|
Btw... just looked on google code... seems like now everything (at least the source code) is online. Is there a way to import old tasks and bugs from SF as well? Simo On Thu, Mar 26, 2009 at 9:41 AM, Simone Chiaretta < sim...@gm...> wrote: > Wow... that is a very long import.. > > 2009/3/25 Phil Haack <ph...@mi...> > >> Still ongoing. It's a slow operation. Once it's in there, I'll give >> access. >> ------------------------------ >> *From:* Simone Chiaretta [sim...@gm...] >> *Sent:* Monday, March 23, 2009 10:43 PM >> *To:* sub...@li... >> *Subject:* Re: [Subtext-devs] No Checkins! >> >> Great... let us know when the change is done. >> Furthermore, can you add me to the project's admins as well? >> Thx >> Simo >> >> 2009/3/24 Phil Haack <ph...@mi...> >> >>> Hi All, >>> >>> >>> >>> I’m going to be moving Subtext’s svn repro to Google Code. Please, no >>> checkins for the time being or they will not be transferred. >>> >>> >>> >>> Phil >>> >>> >>> ------------------------------------------------------------------------------ >>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >>> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >>> easily build your RIAs with Flex Builder, the Eclipse(TM)based >>> development >>> software that enables intelligent coding and step-through debugging. >>> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >>> _______________________________________________ >>> Subtext-devs mailing list >>> Sub...@li... >>> https://lists.sourceforge.net/lists/listinfo/subtext-devs >>> >>> >> >> >> -- >> Simone Chiaretta >> codeclimber.net.nz >> Any sufficiently advanced technology is indistinguishable from magic >> "Life is short, play hard" >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > > > -- > Simone Chiaretta > codeclimber.net.nz > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > -- Simone Chiaretta codeclimber.net.nz Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Simone C. <sim...@gm...> - 2009-03-26 08:41:21
|
Wow... that is a very long import.. 2009/3/25 Phil Haack <ph...@mi...> > Still ongoing. It's a slow operation. Once it's in there, I'll give > access. > ------------------------------ > *From:* Simone Chiaretta [sim...@gm...] > *Sent:* Monday, March 23, 2009 10:43 PM > *To:* sub...@li... > *Subject:* Re: [Subtext-devs] No Checkins! > > Great... let us know when the change is done. > Furthermore, can you add me to the project's admins as well? > Thx > Simo > > 2009/3/24 Phil Haack <ph...@mi...> > >> Hi All, >> >> >> >> I’m going to be moving Subtext’s svn repro to Google Code. Please, no >> checkins for the time being or they will not be transferred. >> >> >> >> Phil >> >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> Subtext-devs mailing list >> Sub...@li... >> https://lists.sourceforge.net/lists/listinfo/subtext-devs >> >> > > > -- > Simone Chiaretta > codeclimber.net.nz > Any sufficiently advanced technology is indistinguishable from magic > "Life is short, play hard" > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta codeclimber.net.nz Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Phil H. <ph...@mi...> - 2009-03-25 17:33:12
|
Still ongoing. It's a slow operation. Once it's in there, I'll give access. ________________________________ From: Simone Chiaretta [sim...@gm...] Sent: Monday, March 23, 2009 10:43 PM To: sub...@li... Subject: Re: [Subtext-devs] No Checkins! Great... let us know when the change is done. Furthermore, can you add me to the project's admins as well? Thx Simo 2009/3/24 Phil Haack <ph...@mi...<mailto:ph...@mi...>> Hi All, I’m going to be moving Subtext’s svn repro to Google Code. Please, no checkins for the time being or they will not be transferred. Phil ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Simone C. <sim...@gm...> - 2009-03-24 05:43:16
|
Great... let us know when the change is done. Furthermore, can you add me to the project's admins as well? Thx Simo 2009/3/24 Phil Haack <ph...@mi...> > Hi All, > > > > I’m going to be moving Subtext’s svn repro to Google Code. Please, no > checkins for the time being or they will not be transferred. > > > > Phil > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta codeclimber.net.nz Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Phil H. <ph...@mi...> - 2009-03-24 02:58:23
|
Hi All, I'm going to be moving Subtext's svn repro to Google Code. Please, no checkins for the time being or they will not be transferred. Phil |
|
From: Phil H. <ph...@mi...> - 2009-03-22 22:18:07
|
2.1.1 wasn't built from the trunk, so feel free to announce it. I did the 2.1.1 work in the Release2.1 branch. So it's our most stable release yet. I'll try to stabilize trunk this week. Phil From: Simone Chiaretta [mailto:sim...@gm...] Sent: Thursday, March 19, 2009 7:38 AM To: sub...@li... Subject: Re: [Subtext-devs] Trunk Problems I think the last two problems are the same I experienced when I tried working on trunk last week. I think they are related to some kind of static variable set at initialization phase. My problem was that when I first installed from scratch and create the blog, I couldn't log in and couldn't see the blog due to some folder being null inside the CurrentBlog object. Then I restarted the app and then everything went fine. But now that Simon says that the problem happens also when you add two blogs, I guess it has something to do with some static variable. But unfortunately I'm busy with the book and cannot look into it in detail. Thanks God the 2.1.1 version of Subtext is has not been announced as usual on all the possible blogs, but only on Phil's one and not as announcement for Subtext but more as POC of installing Subtext via the PI. Simo 2009/3/19 Si Philp <si_...@ho...<mailto:si_...@ho...>> Morning all, Over the last couple of days I have been trying to get the trunk working locally on my works pc. From this I have found the following: * I had a couple of 2.0.0 db's from previous install and the upgrade fails ( can't even get to the page ). o "System.IndexOutOfRangeException: BlogAggregationEnabled" Trunk\SubtextSolution\Subtext.Framework\Data\DataHelper.cs Line: 600 * Couldn't get single blog to work on root. Only worked when I added a folder. * Uploading to a gallery is falling over as the blog.ImageDirectory is null * If I added a second blog all the admin areas for each blog threw a security exception, removing the newly created blogs back to single one and the admin screen worked again. Unfortunately I don't have any more time this week to do more on subtext but thought I would email my findings. Hope to be able to submit a patch or 2 next week. Phil, any idea on when you're moving away from sf? Hope you're all well :) Si ..:: www.siphilp.co.uk<http://www.siphilp.co.uk> | twitter.com/siphilp<http://twitter.com/siphilp> ::.. ________________________________ Windows Live just got better. Find out more!<http://clk.atdmt.com/UKM/go/134665375/direct/01/> ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Simone C. <sim...@gm...> - 2009-03-19 14:38:29
|
I think the last two problems are the same I experienced when I tried working on trunk last week. I think they are related to some kind of static variable set at initialization phase. My problem was that when I first installed from scratch and create the blog, I couldn't log in and couldn't see the blog due to some folder being null inside the CurrentBlog object. Then I restarted the app and then everything went fine. But now that Simon says that the problem happens also when you add two blogs, I guess it has something to do with some static variable. But unfortunately I'm busy with the book and cannot look into it in detail. Thanks God the 2.1.1 version of Subtext is has not been announced as usual on all the possible blogs, but only on Phil's one and not as announcement for Subtext but more as POC of installing Subtext via the PI. Simo 2009/3/19 Si Philp <si_...@ho...> > Morning all, > Over the last couple of days I have been trying to get the trunk working > locally on my works pc. From this I have found the following: > > > - I had a couple of 2.0.0 db's from previous install and the upgrade > fails ( can't even get to the page ). > - "System.IndexOutOfRangeException: BlogAggregationEnabled" > Trunk\SubtextSolution\Subtext.Framework\Data\DataHelper.cs* Line: > *600 > - Couldn't get single blog to work on root. Only worked when I added a > folder. > - Uploading to a gallery is falling over as the blog.ImageDirectory is > null > - If I added a second blog all the admin areas for each blog threw a > security exception, removing the newly created blogs back to single one and > the admin screen worked again. > > > Unfortunately I don't have any more time this week to do more on subtext > but thought I would email my findings. Hope to be able to submit a patch > or 2 next week. > > Phil, any idea on when you're moving away from sf? > > Hope you're all well :) > > > Si > > > ..:: www.siphilp.co.uk | twitter.com/siphilp ::.. > > > > > > ------------------------------ > Windows Live just got better. Find out more!<http://clk.atdmt.com/UKM/go/134665375/direct/01/> > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Subtext-devs mailing list > Sub...@li... > https://lists.sourceforge.net/lists/listinfo/subtext-devs > > -- Simone Chiaretta codeclimber.net.nz Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
|
From: Si P. <si_...@ho...> - 2009-03-19 11:50:36
|
Morning all, Over the last couple of days I have been trying to get the trunk working locally on my works pc. From this I have found the following: I had a couple of 2.0.0 db's from previous install and the upgrade fails ( can't even get to the page ). "System.IndexOutOfRangeException: BlogAggregationEnabled" Trunk\SubtextSolution\Subtext.Framework\Data\DataHelper.cs Line: 600 Couldn't get single blog to work on root. Only worked when I added a folder. Uploading to a gallery is falling over as the blog.ImageDirectory is null If I added a second blog all the admin areas for each blog threw a security exception, removing the newly created blogs back to single one and the admin screen worked again. Unfortunately I don't have any more time this week to do more on subtext but thought I would email my findings. Hope to be able to submit a patch or 2 next week. Phil, any idea on when you're moving away from sf? Hope you're all well :) Si ..:: www.siphilp.co.uk | twitter.com/siphilp ::.. _________________________________________________________________ All your Twitter and other social updates in one place http://clk.atdmt.com/UKM/go/137984870/direct/01/ |
|
From: Phil H. <ph...@mi...> - 2009-03-17 21:56:54
|
Sounds like a good patch idea to me! From: Si Philp [mailto:si_...@ho...] Sent: Sunday, March 15, 2009 11:19 AM To: Subtext Dev List Subject: [Subtext-devs] GalleryThumbNailViewer Evening, I have been playing about with the Gallery side of things for a blog entry and discovered what I think is a limitation. The GalleryThumbNailViewer control uses a datalist which produces some nasty tables. Even in flow mode it's not very pretty. For a more flexible approach can we change this to a repeater? I would submit the patch but thought I would put the question to you guys first. Obviously the change is a quick one on the code side of things but would mean any skins out there would need to be change otherwise it would break. Suppose another option would be to give the skin author the ability to use either a datalist or a repeater? Would appreciate any feedback :) kind regards Si ..:: www.siphilp.co.uk<http://www.siphilp.co.uk> | http://twitter.com/siphilp ::.. ________________________________ Windows Live Messenger just got better. Find out more!<http://clk.atdmt.com/UKM/go/134665230/direct/01/> |
|
From: Phil H. <ph...@mi...> - 2009-03-17 21:56:34
|
Come find me after my talk on Friday if you're at Mix. :) From: Simone Chiaretta [mailto:sim...@gm...] Sent: Tuesday, March 17, 2009 2:24 PM To: sub...@li... Subject: Re: [Subtext-devs] MIX Meetup? I think only Phil will be at MIX this year. Simo 2009/3/17 Travis Illig <ti...@pa...<mailto:ti...@pa...>> Is there a Subtext meetup at MIX? -- Travis Illig http://www.paraesthesia.com ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Subtext-devs mailing list Sub...@li...<mailto:Sub...@li...> https://lists.sourceforge.net/lists/listinfo/subtext-devs -- Simone Chiaretta codeclimber.net.nz<http://codeclimber.net.nz> Any sufficiently advanced technology is indistinguishable from magic "Life is short, play hard" |
755 messages has been excluded from this view by a project administrator.
